Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[corona-dev] FW: Project Join Sequence Diagram
Moving this thread to the Eclipse Corona development mailing list.

From: Kalka, Edyta
Sent: Tue 5/30/2006 9:33 AM
To: O'Flynn, Dennis; Okraszewski, Marcin; Kaczmarek, Pawel; Everitt, Glenn
Subject: RE: Project Join Sequence Diagram

Ok but ….

Looking at this diagram I see the following:

client / team member (org.eclipse.corona.client.project) sends a request called “closeProjectContainer” to the server (org.eclipse.corona.server.ProjectContainerManager) but actually the client do not close the project container residing on a server (?) because there could be other team members working within the same project container space – the client only closes the project opened within his/her workspace (in other words the client logs out or disconnects from the server).

 

From: O'Flynn, Dennis
Sent: 30 maja 2006 15:11
To: Kalka, Edyta; Okraszewski, Marcin; Kaczmarek, Pawel; Everitt, Glenn
Subject: RE: Project Join Sequence Diagram

 

The first column of the sequence diagram is a client side component (name: org.eclipse.corona.client.project).  This component will interact with the corona server-side (name: org.eclipse.corona.server.ProjectContainerManager) via web services.

 

In the current demo, there is some "magic" to create an ECF group based upon the project's name.  This is required to initialize ECF resources so that project collaboration can take place.  This will be replaced with the call to openProjectContianer.

 

From: Kalka, Edyta
Sent: Tue 5/30/2006 8:10 AM
To: O'Flynn, Dennis; Okraszewski, Marcin; Kaczmarek, Pawel
Subject: RE: Project Join Sequence Diagram

 

Yes, we’ve reviewed it.

It is general view of the message sequence – however I have few comments:

-          there are requests going from client to project container manager called openProjectContainer, closeProjectContainer – from my point of view project container is something residing on server. New client (team member) can join existing project container but not open it or close it – instead he/she can open or close project (but not project container) – it is just comment concerning used naming

-          when team member opens the project there should be an event posted (e.g. activateUser) meaning that this user is now connected and available for other team members, likewise when team member closes the project some event (e.g. passivateUser) should be posted informing that this user is disconnected

 

What do you think?

 

Edyta

From: O'Flynn, Dennis
Sent: 30 maja 2006 13:15
To: Okraszewski, Marcin; Kalka, Edyta; Kaczmarek, Pawel
Subject: Project Join Sequence Diagram

 

Did any of you get a chance to review the sequence diagram for the next use case?  If so, any comments?

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

Back to the top