Hi You are right, the info sent with Data API does not include user data - blip read/unread state is not included. You do though, have the last modified date, so you can navigate the blips in this order - take a look at micro-box.appspot.com. (source at https://github.com/vega113/microbox). The data documents are not in use, so they are always null. Anyway, data documents were initially supposed to add ability to attach a custom data to a blip (like a custom XML file), but I think it was never correctly implemented even in Google Wave. The native Wave client uses different protocol to fetch the data from the server so it has access to the user data wavelets.
So regarding your second question: Robot/Data API are not live, and use simple event based HTTP requests/responses. The native Wave client is live and uses protobuff messages over websockets/ socket.io to communicate with server but there's no well defined API. In theory you can create your own client that makes websocket calls but that will not be easy. On Fri, Nov 8, 2013 at 12:13 PM, Felix Wackernagel < felix.wackerna...@gmail.com> wrote: > Hi, > i have two question about the Java Client API. > > 1) I load all Wavelets from a Wave and found only the information how > many message of a wavelet is unread but not which one is unread. I read > in the Whitepapers about a User-Wavelet which stores such informations. > I use the getDataDocuments() method on the Wavelet but it is everytime > empty. Exist another way to get this informations or is some extra calls > needed to the data model? > > 2) And the second one is abount the real-time comunication. The Java > Client uses a simple HttpClient which creates for everytime a seperate > connection between client and server. But i read that this comunication > uses WebSockets to send messages from server to client automaticly. It > is possible to make a WebSocket call to the waveinabox.net server? > > I hope some one can help me to bring a little bit more light in the wave > secrets. > > Best regards, > Felix >
