Got it, thanks. Its been renamed too "Client/Server protocol: XMPP versus JSON versus other", which is probably why the search didnt work.
~~~~~~ Reviews of anything, by anyone; www.rateoholic.co.uk Please try out my new site and give feedback :) 2009/10/15 Joe Developer <[email protected]>: > try searching for 'with:[email protected]' > Make sure that you are on the 'new preview' server not the dev preview one > This link may > help: https://wave.google.com/wave/#restored:search:with%253Awave-protocol%2540googlegroups.com,restored:wave:googlewave.com!w%252B7hegIf3CF > > On Thu, Oct 15, 2009 at 5:31 PM, Thomas Wrobel <[email protected]> wrote: >> >> "The new client/server protocol" isnt coming up in my search :-/ >> (also tried a few variations of that). >> >> Is it tagged wavedev? >> ---- >> @Owen: Yes, that does sound a bit similiar in some functionality. We >> are very keen on the playback feature also. >> We like the idea of being able to see the state of a "world" a few >> days back, or to watch a 3d construct being built piece by piece in as >> you play. (of course, as they are remote-linked assets controlled by >> the client that submitted them, this wouldnt be true playback, and the >> state of the remote link might not have its own history....but even >> without that it would still be interesting to see things being >> constructed over time. >> >> >> 2009/10/15 Dale Francis <[email protected]>: >> > There is a new thread for the discussion, created by myself and another >> > guy. >> > it has been split into multiple threads and is better organised so this >> > wont >> > happen and its more specific discussion >> > It's called The new client/server protocol discussion, everyone in this >> > group has access just search for it :) >> > >> > >> > On Thu, Oct 15, 2009 at 12:00 AM, ThomasWrobel <[email protected]> >> > wrote: >> >> >> >> sorry, I did skim this thread, but missed that. >> >> I can access the Wave now, but it seems read-only (says its too large >> >> or a message is too long) is this the same for everyone now? >> >> >> >> On Oct 13, 10:28 pm, Michael K <[email protected]> wrote: >> >> > On Oct 13, 11:13 am, Stefan Langer <[email protected]> >> >> > wrote: >> >> > >> >> > > So if I understand it correctly you are writing this library for >> >> > > the >> >> > > server >> >> > > side of things and not for the client side? >> >> > >> >> > I'm not actually writing it yet - but I want to. I still have a few >> >> > other things I need to finish first before I can get to this. >> >> > >> >> > As I wrote in my message from Oct 12, I want to take the console >> >> > client that comes with FedOne, and extract *the client's* >> >> > communications layer into a library (and then wrap it in a higher- >> >> > level API). So this is for the client side. >> >> > >> >> > @jesus salas, Thomas Wrobel - please read my message from Oct 7 >> >> > regarding the address of the discussion wave and what to do if you >> >> > have trouble loading it. You should also take the time to read this >> >> > thread from the beginning to get our bearings. >> >> >> > >> > >> > > >> > >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
