My understanding is that the Robots API is exposed externally, but
WaveBus is an internal interface.
https://svn.apache.org/repos/asf/incubator/wave/trunk/src/org/waveprotocol/box/server/waveserver/WaveBus.java
Dave
On 18/06/13 13:53, John Blossom wrote:
Thanks for the diagram, Dave, it helps me to visualize Wave's components.
How much is the "wave bus" a reality as opposed to a potential division in
programming? That is, in terms of how one binds/opens the bus, does it
really function as an API.
John Blossom
On Sun, Jun 16, 2013 at 12:11 PM, Dave <w...@glark.co.uk> wrote:
I couldn't find an overview of the various bits of the wiab server, and
how they plumb together. So from a couple of hours digging into the
codebase, I knocked up the attached diagram.
I didn't include the Concurrency and Document/Conversation structure, as I
suspect these are better visualised differently / separately.
Is there anything inaccurate or that should be added this diagram, and is
it worth including in the wiki?
Dave
