Well, debugging on GAE is a little painful, but from what I can see the robot is NOT seeing any events related to document modify. What I can see from the wiab server log on the passive api side, is a log message stating "no events" when undercurrent replies are created. The robot responds to its commands using BLIP_SUBMITTED, which works on the production wave server (and sandbox as well). I hope this helps.. I'm a bit puzzled by all this for the moment.
On Tue, Nov 2, 2010 at 6:14 PM, Lennard de Rijk <[email protected]>wrote: > > > On Tue, Nov 2, 2010 at 3:49 PM, Matt Richards <[email protected]> wrote: > >> With an updated copy of the Python robot API library, and the correct >> token set.. I am now able to use DOCUMENT_MODIFY on the Active API, great >> progress. >> If I'm not mistaken a lot of document operations have now been submitted >> to tip (I was using a manual patch from the code review page). >> > > Correct, most of them are converted into the document.modify op (at least > for Java). I kind have the feeling the others are out deprecated but never > marked as such. Could you tell me wether the python api spews out anything > with regards to document.* operations, except those involving blips. > > Greetings, > Lennard > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- --Matt -- You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en.
