Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [corona-dev] Team member view. 
I'm not clear why PC-Mgr would provide this method:
boolean getIsOpened (String uriString);

The PC-Mgr manages many containers for many users.  The PC-Mgr keeps
track of whether a container is loaded or not.  If one user already has
it open and another user issues an open, a reference count for the
container is updated the same container is not load twice.  I don't
understand why the PCX which requested the container open/close on
behalf of a user wouldn't track the open/close status for the user?  Is
there a reason for the server side to know whether a user has a project
is opened or closed?  An event will be sent when the user opens/closes a
container.

If we need to track users and know which containers a particular user
has open I think that would go into another object like a UserManager.
For now, I think this information can be kept in the client platform.

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kaczmarek, Pawel
Sent: Thursday, August 03, 2006 8:29 AM
To: Corona development
Subject: RE: [corona-dev] Team member view.

If PC-Mgr manages opens / closes of PCs, it needs to supply methods for
PCX to manage this information:
	boolean getIsOpened (String uriString); // uriString - uri of PC
	openPC (String uriString);
	closePC (String uriString);

Pawel

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
Sent: Thursday, August 03, 2006 1:50 PM
To: Corona development
Subject: RE: [corona-dev] Team member view.

Yes - the PCV's Team Member List should be dynamic (not static).

The PC-Mgr will publish a ProjectEvent each time a user (via PCX) has
opened or closed a PC.  This event will be shared with everyone in the
workgroup.  The event properties should contain information that
identifies who has opened or closed the PC.  This information can be
used by the Team Member List to allow it to update itself.

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
Sent: Thursday, August 03, 2006 7:51 AM
To: Corona development
Subject: Re: [corona-dev] Team member view.

Note that the team list is static now. Should I refresh it as some event

arrives? If yes, which event would it be?


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. 
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev

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. 
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev

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. 
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev

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