Thanks cmdskip for the suggestion, I've adapted my capabilities.xml as you suggested. Unfortunately that doesn't seem to have changed the number of blips I can read through (for my robot at least).
S On Nov 23, 10:04 pm, cmdskp <[email protected]> wrote: > Good day, Stephen! > > Have a look at the reply I just left on that thread "How to delete all > the blips in a wave except the root blip??" > > I'd given a shorter version of how the event design for robots is > specified before on the issue tracker to help Olreich a few days ago. > > In essence you can (currently as of last night anyway) retrieve (I > believe) all the blips (it worked for my robots) for > WAVELET_SELF_ADDED - but make sure you have the extra attribute > context="children" as well as content="true" in your capabilities.xml > for that event. > However, this is a moving target - it used to be you couldn't get all > the children, but a bug was fixed recently and it seems now you can - > though I've not checked getting inline blips. > > On Nov 24, 12:08 am, Stephen George <[email protected]> wrote: > > > ...I believe I found the answer to my question from Olreich's helpful > > post here: > > "How to delete all the blips in a wave except the root blip??" <http:// > > groups.google.com/group/google-wave-api/browse_thread/thread/ > > 8b63dc678eafa93d/cb9991744f26ab59?#cb9991744f26ab59>. > > > When your robot receives an event about an updated Blip, you can > > expect to receive context of only a limited number of parents, > > children, and siblings. This is to reduce the sheer size of the json > > payload that the Wave server sends to your robot. Certainly, > > transmitting the entire structure and content therein of a full Wave > > with every subscribed event would be daunting for a large-sized Wave. > > > Makes sense, though it would be helpful to have at least a means of > > receiving the full Wave structure, in the (hopefully seldom) instances > > where your newly-added robot wants to read-up on all of the content > > that it has been created before it began to participate in the Wave. > > > S > > > On Nov 22, 9:37 pm, Stephen George <[email protected]> wrote: > > > > By the way, I too am having difficulty trying to traverse every blip > > > of a wave in Java. > > > > My current approach of recursively searching through every blip with > > > blip.getDocument().getInlineBlips() and blip.getChildren() is not > > > completely successful. I seem to get only the first 2 out of 7 > > > sequential Blips. Blip 3 is there, but it's content is not in the > > > object. > > > > Here's the structure of my test Wave (all blips are sequential - no > > > inline blips): > > > > message 1 > > > -------- > > > message 2 > > > -------- > > > message 2 > > > -------- > > > message 2 > > > -------- > > > message 5 > > > > Here's the one capability that I'm listening for: > > > <w:capability name="WAVELET_SELF_ADDED" > > > context="PARENT,SIBLINGS,CHILDREN" /> > > > > And here's the logging output from my Servlet: > > > > getBlipId(): b+xIimGfd3C > > > getParentBlipId(): null > > > hasChildren(): Y > > > getLastModifiedTime(): Mon Nov 23 01:57:03 UTC 2009 > > > getDocument().getText(): message 1 > > > ****** > > > getBlipId(): b+xIimGfd3D > > > getParentBlipId(): b+xIimGfd3C > > > hasChildren(): Y > > > getLastModifiedTime(): Mon Nov 23 01:57:13 UTC 2009 > > > getDocument().getText(): message 2 > > > ****** > > > getBlipId(): b+xIimGfd3E > > > getParentBlipId(): b+xIimGfd3D > > > hasChildren(): N > > > getLastModifiedTime(): Wed Dec 31 23:59:59 UTC 1969 > > > getDocument().getText(): > > > > It's possible I may be doing something wrong. I'd be happy to post my > > > code for review, if you guys have the patience to read it. :) If > > > someone could tell me if they are having similar issues trying to > > > traverse an entire Wave, that would be helpful too. > > > > Thanks, > > > > Stephen -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
