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) 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). On Wed, Dec 2, 2009 at 3:40 PM, Beldar <[email protected]> wrote: > 1) You can save data in the appspot database > > 2) In Python you can get outside data with the urllib, for example > urllib.urlopen('http://someurl.com'). > > On Nov 30, 10:32 pm, gruszczy <[email protected]> wrote: >> Hi! >> >> I would like to create a robot, that would be able to monitor activity >> in our mercurial repository and post information about new commits. >> Therefore I have two questions: >> >> 1) how to provide some additional configuration for the roboty? I >> could simply write user/password data in plaintext in a wavelet, but >> that doesn't seem as a reasonable idea. >> >> 2) is it possible for the robot to somehow communicate with the >> outside world and retrieve information about hg changes? >> >> I'd really love to make such a robot, because this way we would be >> able to use it in all our coding projects, that we would like to >> discuss on 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]. > 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.
