> > > It's almost certainly what the user wants anyway. > Its just that the watches are pretty lightweight and sending bytes around > is > just more work to do at the server. Though we should experiment with how > much more load it generates and how useful would it be to send out the > bytes > with the event of nodedatachanged and nodecreated. >
It might just be an alternate method... maybe not returning the data by default. It would solve the issue of deletes after NodeDataChange .... Kevin -- Founder/CEO Spinn3r.com Location: San Francisco, CA AIM/YIM: sfburtonator Skype: burtonator Work: http://spinn3r.com
