Thanks Ali, My day to day work doesn't include much Java, but I have harbored an interest in OSGi for quite some time.
Is there any other interest out there in identifying a subcomponent of the current implementation that might work as a bundle? If there's any curiosity at all, I'll take a stab at pulling something together. -R On Tue, Jun 18, 2013 at 9:22 AM, Ali Lown <a...@lown.me.uk> wrote: > Ryan, > > Having never used OSGi Event Admin in a project, I can't speak for certain. > > A quick Google to see its use suggests the pub/sub model behind them > both is the same, so you could say that it is similar. > > Ali > > On 18 June 2013 16:13, Ryan Hill <r...@zndx.org> wrote: > > Hi Ali, > > Without advocating for anything, do you think WaveBus is at all similar > to > > OSGi Event Admin? Just being curious... > > > > Thanks, > > --Ryan > > > > > > On Tue, Jun 18, 2013 at 7:57 AM, Ali Lown <a...@lown.me.uk> wrote: > > > >> Yes. > >> > >> Originally, the WaveBus was how GWave components was split between > >> different machines, so had an ethernet-backed implementation and made > >> a lot more sense than it does currently. > >> > >> Now, it is simply a convenient abstraction to inform modules of > >> WaveletUpdate and WaveletCommits around the whole server. > >> > >> On 18 June 2013 14:54, Dave <w...@glark.co.uk> wrote: > >> > 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 > >> >>> > >> > > >> >
