But then I'll have to go through the entire process of establishing a connection with the wave server myself, which would be a bit of a gnarly process I imagine.
On Dec 10, 10:13 am, Raphaël Pinson <[email protected]> wrote: > Hi Martin, > > Even now, you should be able to achieve what you want to do using > crontabs. Appengine lets you call your script with cron, so what you > could do is: > 1) When the bot is called in a Wave, store the WaveID in the datastore > 2) When the bot is called from cron, get all WaveIDs from the > datastore and do your proactive work. > > Raphaël > > On Thu, Dec 10, 2009 at 1:12 AM, martin <[email protected]> wrote: > > Goodo, I shall await eagerly. I have some rather cool ideas I want to > > test using this ;) > > > On Dec 9, 11:56 pm, "Austin Chau (Google employee)" > > <[email protected]> wrote: > >> Can't give ETA but I can say "soon" :) > > >> On Wed, Dec 9, 2009 at 3:49 PM, martin <[email protected]> wrote: > >> > As ever google is one step ahead of me ;) > > >> > Any idea when that will be done (days/weeks/months)? > > >> > On Dec 9, 11:45 pm, "Austin Chau (Google employee)" > >> > <[email protected]> wrote: > >> > > Hi Martin, > > >> > > In fact we are actively working on the "active" API as we speak :) > > >> > > When it is polished enough we will update the docs with cut new client > >> > > libraries for it. Thanks for the patience. > > >> > > Austin > > >> > > On Wed, Dec 9, 2009 at 3:33 PM, martin <[email protected]> wrote: > >> > > > As far as I can see, at the moment robots are limited to being > >> > > > entirely reactive, ie. they can only make a change to a wave when > >> > > > something else happens. Is it possible for a robot to be proactive > >> > > > and > >> > > > initiate changes in a wave without an event in the wave triggering > >> > > > it? > >> > > > I wonder this because I want to use a robot as an interface between a > >> > > > service and wave, when the wave changes the service should be > >> > > > informed > >> > > > (the robots catches the changes, converts them into the correct form, > >> > > > and sends them on) and when something in the service changes it pings > >> > > > the robot which would then apply this change in the correct format to > >> > > > the wave. > > >> > > > -- > > >> > > > 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]<google-wave-api%[email protected]> > >> > <google-wave-api%[email protected]<google-wave-api%[email protected]> > > >> > > > . > >> > > > For more options, visit this group at > >> > > >http://groups.google.com/group/google-wave-api?hl=en. > > >> > -- > > >> > 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]<google-wave-api%[email protected]> > >> > . > >> > For more options, visit this group at > >> >http://groups.google.com/group/google-wave-api?hl=en. > > > -- > > > 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 > > athttp://groups.google.com/group/google-wave-api?hl=en. -- 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.
