> > >> This is a difficult problem but I don't think we need to arrive at a good > solution immediately. Something like (c), perhaps without the rewind, is a > reasonable start. This will be a very infrequent occurrence. If deltas are > rejected due to permission failure just freeze the panel so the user can't > keep typing, and tell them what happened. Give them the opportunity to > copy/paste their fresh content if they want before closing the wave, but > then they're done. >
As long as the user is working online there is no real problem with freezing the wave panel because the user gets almost immediate feedback. Should we ever support real offline work, i.e. allow for deltas to be stored in a HTML5 store, then the damage caused by such an incident can be high (stored deltas are lost because a delta in front of them had a problem) and fixing it is difficult. > > Basically, I don't think this needs to be solved at the protocol level. > It's an application problem. > I do not believe that missing error semantics and missing error codes are an application problem. The protocol must at least state what kind of error this was. Torben > >> >> Torben >> >> >> >>> Implementation in the server shouldn't be that complicated. >>> >>> -Tad >>> >>> -- >>> 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]<wave-protocol%[email protected]> >>> . >>> >>> For more options, visit this group at >>> http://groups.google.com/group/wave-protocol?hl=en. >>> >> >> >> >> -- >> --------------------------- >> Prof. Torben Weis >> Universitaet Duisburg-Essen >> [email protected] >> >> -- >> 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]<wave-protocol%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/wave-protocol?hl=en. >> > > -- > 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- --------------------------- Prof. Torben Weis Universitaet Duisburg-Essen [email protected] -- 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.
