Yes, private replies need to implemented as a separate wavelet, as do any access control mechanisms within the same wave (which, if I understand correctly, you are looking to do for your specification example). I was just surprised that you needed something like this for your client, swing or otherwise. In any case, taking a step back, what evidence do you have that the wavelet hasn't been added to the wave? Both on the client side and the server side. Also, could you verify by looking at the server logs that the server either isn't getting the update from the client, or isn't sending the update back to the client.
-- Ben On Mon, Aug 24, 2009 at 10:48 PM, tobber harley <[email protected]>wrote: > > Hi Ben, > > Thanks for your fast answer!!! I changed the syncWithIndexWave method > as you said, > and it compiled well, but I still got the same problems. I think the > new wavelet isn´t > created on the server, only on my client. > > >>However, in any case -- why do you want to allow multiple conversation > >>wavelets per wave? > > a wave represents a topic, e.g. a system specification, the first > wavelet > could be a discussion about the specification document, and the second > wavelet could be the > specification document itself. I hope you understand what I mean :) > > And how would you otherwise realize a private reply inside your wave ? > > Why does the java robots api provide methods for creating new wavelets > (Wavelet.createWavelet) ? > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
