I apologize for my lack of information, though Mr. Nesting was able to help me despite my neglect. I am using the Java API so I suppose he either assumed that was what I am using or there is a similar API for Python. I have since gotten the hang of storing data using the setDataDocument method and then accessing that data with the appropriate related methods. Although I DO have a minor question. Would you or anyone else happen to know if there is a cap on the number of data documents I can store for a single wave? Or if there is a size cap?
On Oct 18, 1:32 pm, atc <[email protected]> wrote: > On Oct 18, 5:57 pm, Smola <[email protected]> wrote: > > > I need a way for information my robot gathers to persist. So, let's > > say I want to find a blip and save its ID so I can work with it in the > > future. I don't know how to do that currently. I know how to find > > the ID of a blip, but I do I save it for later use? Or, if I create > > an object in response to an event, how do I save all of the properties > > of that object as they are affected by more and more incoming blips? > > What language are you using? > > > Is the object automatically saved on the server when my robot is added > > to a wave and then stays there the rest of the time? It would seem > > that if waves are to exist forever in my archive that that would take > > up quite a bit of space down the road. > > The persistence probably comes from using the datastore provided by > Google App Engine. > > Provide a bit more information first and perhaps people can help. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
