Won't you still have handle storage and routing all traffic through your own server when using Federation? This is what I'm trying to avoid.
On Mar 13, 9:35 pm, Nicolas Toublanc <n.toubl...@gmail.com> wrote: > Or an open source Web Wave client implementation? > > Actually, we have the following projects in open-source: > > - servers: > - FedOne (initiated by Google): > > http://code.google.com/p/wave-protocol/wiki/<http://code.google.com/p/wave-protocol/wiki/FedOne> > FedOne <http://code.google.com/p/wave-protocol/wiki/FedOne> > - PygoWave:http://pygowave.net > - clients: > - Console client (initiated by Google) : > http://code.google.com/p/wave-protocol/wiki/ConsoleClient > - PygoWave Desktop client :http://pygowave.net/blog/?p=117 > > None of theses projects is usable as official closed-source project is. > > However, they are in active development (FedOne just got persistence via an > external contribution) and very interesting project. > > Why don't share libraries with theses projects and create a new web-app UI? > > On Sat, Mar 13, 2010 at 9:13 PM, Joe Gregorio <j...@bitworking.org> wrote: > > It sounds like what you want is Google Wave Federation, which is > > described here: > > > http://www.waveprotocol.org/ > > > Thanks, > > -joe > > > -- > > Joe Gregorio > > Developer Relations, Google Wave > > > On Wed, Mar 10, 2010 at 1:31 PM, trond <tolse...@gmail.com> wrote: > > >> This is probably outside the scope of Google Wave, but have there been > >> any thoughts about opening up communications with Google Wave "to the > >> outside". I'm not thinking about robots that automate stuff, but > >> letting users manipulate their Wave data in other javascript/client > >> applications. Like using Google Wave as a generic storage solution. > >> Now, I do see some obvious problems like introducing unknown > >> dataformats etc., but I really think this could be a good > >> "collaborative storage solution" for all kinds of web-applications to > >> work against. Though it's maybe not what Google Wave is about. :) > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Google Wave API" group. > >> To post to this group, send email to google-wave-...@googlegroups.com. > >> To unsubscribe from this group, send email to > >> google-wave-api+unsubscr...@googlegroups.com<google-wave-api%2bunsubscr...@googlegroups.com> > >> . > >> 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 google-wave-...@googlegroups.com. > > To unsubscribe from this group, send email to > > google-wave-api+unsubscr...@googlegroups.com<google-wave-api%2bunsubscr...@googlegroups.com> > > . > > 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 google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
