Hi, code-laboration is working on a project that uses WIAB as the core
framework, but with modifications to the UI and the UX. We saw that there
were just some talks about modularisation, and had actually been thinking of
the same thing for the past several days. We had talked to Yuri the other
Thanks for putting this together. It's great that you are interested in WiaB.
To answer one of your questions, this kind of document really should be posted
on the apache incubator web site. However, I have been struggling with how we
should really manage this web site. The Apache CMS is a
Hi Michael,
thanks for taking the time to read the doc, your comments are very
appreciated, as you know well the application and you can help us clarify.
Well, first of all I have to say that we are newcomers to Wave project, so
we are trying to put together information as we learn from different
David recently described the current c/s protocol to me when I was
trying to understand it;
The messages are JSON, and their structure is defined by some protos, and
enveloped as (see WaveWebSocketClient$MessageWrapper):
{ sequenceNumber: unused I think, messageType: message class name,
Thank you very much for the valuable information, Thomas. This is exactly
the kind of feedback we was wanting to receive, we will modify the document
immediately to make it more accurate, and also will incorporate this
detailed information to another document where the current c/s protocol will
be
Hi, code-laboration is working on a project that uses WIAB as the core
framework, but with modifications to the UI and the UX. We saw that there
were just some talks about modularisation, and had actually been thinking of
the same thing for the past several days. We had talked to Yuri the other
Regarding modularization - there were talks about using Maven to manage WIAB
dependencies and introduce better modularization of the code. It might be of
interest to you -
Ive always thought modularisation is a very good idea, but in that
diagram I'm a little confused as it shows the GWT client communicating
with the server via the wave-protocol - I'm not sure this is right?
The wave federation protocol is for serverserver, the clientserver
uses (and will use)
Regarding the documentation you willing to share: I think that if you could
to put it on Google Docs or Google Wave for public review - then it can be
pushed into the Apache Wave Wiki by one of the committers.
Thanks for your willingness ton contribute!
2011/7/21 Michael Lilly
