Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ormf-dev] First cut on OSGi based server architecture diagram 
Hi,
I have progressed this some, but not quite as much as I would have liked this week. Iac, please take a look at the document to date, comments would be appreciated. I have also sent along the two diagrams seperately so that you have good quality ones. Btw, the diagrams are complete except for changes in response to comments, it is the document that still needs quite a bit of work. 

Joel

Attachment: ORMF architecture in brief.pdf
Description: Adobe PDF document

Attachment: high level architecture.pdf
Description: Adobe PDF document

Attachment: proposed component and services architecture.pdf
Description: Adobe PDF document


On 14 Oct 2008, at 19:54, Joel Rosi-Schwartz wrote:


Hi,
I will be checking this into SVN fairly soon, but I thought I would make it easy on everyone and give you a look at the architectural diagram I am doing.
In the client the the boxes are simple classes (which in fact already exist) that are responsible for communicating with the server. The components are, of course, OSGi bundles (or Eclipse plug- ins, if you prefer) and the ovals within them are OSGi services. The lines of course indicate dependencies. Note that for service bundles, there are no dependencies on packages in the bundle, everything happens via calls to the OSGi services. On the other hand, the "Shared Code Bundles" do export packages to both the client and server bundles; these are not shown explicitly because they are rather ubiquitous and thus would clutter the diagram.
Tomorrow I am going to start creating a brief architecture document for the server, something in the order of several pages. Just enough to give everyone an essential understanding of what is happening where. This will get fleshed out over time.
I mentioned during the team conference that I had plan up my sleeve to start getting everyone directly involved in the "real" development. What I suggest is that each of us takes ownership of one of the top level services on both the client and the server. How convenient that there are seven remote services and seven of us; I love it when a plan comes together :-) I think this is a fabulous way for everyone to get familiar with the system and to be making a concrete contribution on moving us forward.
Start thinking about it and let me know if you have any specific preferences. To be clear I am speaking about Server, Project, Collection, Document, Relationship, LOV, Administrator; in each case the Delegate, the RemoteService and the Service, including all ancillary classes in each services bundle.
After we have this absorbed, which I expect to take all of iteration 1, we will start looking at dividing up the internal services. We have to make sure, though, that we leave some resources available for the GUI :-) 

Your thoughts and comments please.

Joel
PS - I am cc'ing Jojy and Yahya because I am not certain if they are on the ormf-dev list. Could both of you please confirm that you are. - thanks 


<proposed component and services architecture.pdf>
_______________________________________________
ormf-dev mailing list
ormf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ormf-dev

Back to the top