If the client implements the OT API, you should be able to traverse
revisions using only the deltas. In regards to the character-by-character
level of real-time updates, all you would need is an onkeydown event that
transmits each character as a characters() command that only inserts one
character at a time. The "blip" wouldn't be partial, per se, but the client
would have the ability to understand it that way according to
client-specific business rules.
For example, a new blip opened on the client would immediately be sent as an
elementStart("b");elementEnd(); command, then each character inserted would
be sent as a retain(x+charsInserted);characters('char'); command. For UI
semantics, a client could insert a custom tag or token as an immediate child
of a blip as soon as it is opened for insert or update, and remove said tag
or token as soon as a newline event was received. This would identify the
blip as being in an "in-progress" state. Other clients that are implemented
in such a way to recognize this method would be able to represent this as
"X-User is typing...". Whenever they receive a "deleteElement();" event,
they would simply remove the message.Mark Adamcin (480) 201-4448 [email protected] On Sun, Oct 4, 2009 at 4:43 PM, Dale Francis <[email protected]>wrote: > Not to sure about it either dude, it could possibly be a combination of > both. The playback is to show each 'Blip' in the wave as it happened. > possibly there is a way to create a partial blip or a blip in progress and > thats how we see it typing. Again not sure either havnt really seen wave yet > :( > > > On Mon, Oct 5, 2009 at 9:26 AM, Christoffer Hallas Pedersen < > [email protected]> wrote: > >> Im pretty sure you can't setup a stream of data and simple read the data >> as it is sent from a OnKeyDown event. I get this because Wave is supposed to >> support history (replay), and i think that would only be reasonable if every >> history of the wave is stored as revisions, and a revision of a wave being a >> fully formatted wave with all the XML and stuff around the actual message. >> Besides, you would only have to update the current wavelet, which really >> isn't that much data. >> However, i'm not sure about this at all. >> >> Christoffer >> >> >> On Mon, Oct 5, 2009 at 12:17 AM, Dale Francis <[email protected]>wrote: >> >>> Are you sure? doing it that way would generate alot of data between the >>> servers and clients. i thought one of the ideas behind Wave was to 'make it >>> fast'? again i may be wrong so dont quote me on it :) >>> >>> >>> On Mon, Oct 5, 2009 at 8:02 AM, Christoffer Hallas Pedersen < >>> [email protected]> wrote: >>> >>>> Isn't it possible to change the Wave locally and send out a ping to >>>> other Federation servers who are currently engaged on the Wave, so its up >>>> to >>>> the ping receiving fed servers to ask for an update if they're still >>>> interested in the Wave (read: the Wave is still open) ? >>>> >>>> >>>> On Sun, Oct 4, 2009 at 10:30 PM, Dale Francis >>>> <[email protected]>wrote: >>>> >>>>> This may be a little naive of me, but wouldnt that be as simple as >>>>> using the protocol and GWT and create a JSO on page load that was a >>>>> connection/stream (sorry im a .net developer not sure what its called in >>>>> java) to the server and on the OnKeyStroke event you sent it back to the >>>>> server. >>>>> The server updates the waves xml everytime it recieves a >>>>> blip/communitcation from the client so as long as you handle the incoming >>>>> Wave XML you should be fine. >>>>> With showing who is typing what, i am not 100% sure, have a look at the >>>>> incoming wave xml and see if it gives you anything, or potentially does >>>>> the >>>>> API have anything that could handle this? >>>>> >>>>> >>>>> On Sat, Oct 3, 2009 at 6:44 AM, Nico <[email protected]> wrote: >>>>> >>>>>> >>>>>> So, I installed the fed one server, then looked into Thomas gui >>>>>> desktop client and the google one and built a desktop client for >>>>>> myself. Then I built a Java Servlet that connects to the fed one >>>>>> server and I am able to chat from html (just sending lots of ajax >>>>>> requests to the servlet) in a very rudimentary way. >>>>>> >>>>>> I also asked Scott Hamilton on another post that built a jsf >>>>>> implementation of the client, he was great and let me see his code >>>>>> (though I didn't use it at last) >>>>>> >>>>>> Now, I am trying to do the real time character by character chat, but >>>>>> I am having a lot of trouble there, has anyone tried to do it? either >>>>>> desktop or html, I would like some advice there, I am pretty stuck >>>>>> right now. >>>>>> >>>>>> I would appreciate any help!. >>>>>> >>>>>> On another topic... I've signed to the sandbox and the preview to try >>>>>> and see how their client looks and works, but never got in, and I have >>>>>> checked and the embedded client does not work with our own fed one >>>>>> servers. Did anyone managed to use the embedded client? >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
