2009/12/3 Filip Gruszczyński <[email protected]>: > I am > > 2009/12/2 Raphaël Pinson <[email protected]>: >> Hi, >> >> Like Beldar suggested, you could : >> >> 1) Store the waveID, user and passwd in the datastore (or just a URL >> in hg I guess would be enough) > > I know, that I can store this, but how user in wave is supposed to > provide this? Some kind of a dialog would have to pop up, where user > could provide username and password.
In my case, I currently use a language to speak to the bot. Many bots do that, for example you could have <commity add 'URL' 'user' 'passwd'> or whatever format you prefer. You could also use a gadget to let people enter data and then get the gadget values when it is modified. > >> 2) Run your script in cron (otherwise you depend on the Wave being >> updated to post about new commits). For each conf stored in the >> datastore, achieve a checkout on the URL using urllib.open and update >> the wave (using the waveID stored in the datastore for the conf). > > This is a good idea. It should work, if only I can do this > asynchronously - if robot keeps conf for multiple hg repos, it can > take a lot of time to retrieve all information. Or maybe I could run a > few processes, that would do that? > > -- > Filip Gruszczyński > > -- > > 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. > > > -- 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.
