Outside of some advice on when to code a gadget versus a robot ( see
http://code.google.com/apis/wave/extensions/ ) and the overall
architecture of the protocol itself ( see
http://www.waveprotocol.org/whitepapers/google-wave-architecture ), I
could not find much in the way of architectural best practices for
writing wave extensions.

What is the architecture for your wave extensions? What works and
doesn't work about your architecture?

--

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.


Reply via email to