Hi Andres For the moment do not think release the source code, but I can make a diagram of the architecture and code examples of using this architecture. Of course you can help me in testing, but is still a prototype. I hope in 15 days more to have the first version that works.
Matias 2009/12/15 Andrés Cerezo <[email protected]>: > It's very good can we see the source code or the architecture graphically ? > Can I help you with testing? > > > 2009/12/12 gengstrand <[email protected]> >> >> That's very cool, Matias. Thanks for posting. Is the Spring app >> somehow running in Google App Engine or as a stand alone web app? How >> are you sharing data between the robot and the Spring app? >> >> On Dec 11, 11:52 am, Matias Molinas <[email protected]> wrote: >> > I am developing an application that uses Wave as a way to provide >> > services for Gadgets and Wave users, so I'm using a 3 layer >> > architecture with Spring MVC, where the Wave Robot (Servlet) is one >> > component of my layer IU. >> > >> > I use Gadgets and are components from my UI layer that consumes the >> > services of my Robot. >> > >> > I think it's a good architecture for a Wave extension. >> > >> > My application (www.bubaproject.com) is still under development, but I >> > did some tests to validate the architecture of Google App Engine and >> > I'm happy with the choice. >> > >> > 2009/12/11 gengstrand <[email protected]>: >> > >> > > 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 >> > > 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. >> >> > > -- > > 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.
