RE: [corona-dev] Ref count for container.

["O'Flynn, Dennis" <Dennis.OFlynn@xxxxxxxxxxxxx>]

Some of the information is ContextContainer specific, such as
open/close.

Other data is for ProjectContainer, such as User presence, etc...

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Everitt, Glenn
Sent: Wednesday, March 14, 2007 9:04 AM
To: Corona development
Subject: RE: [corona-dev] Ref count for container.

What keeps track of Clients - since a ClientID may reference many
Containers.  If I understand...

So, do we need to define semantics for? 
Client - open, close
User - on, off
Container - open, close
User in a Container - yes, no

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
Sent: Wednesday, March 14, 2007 8:55 AM
To: Corona development
Subject: RE: [corona-dev] Ref count for container.

+1 for using an ID, not user.

The ref count was / is intended to identify the number of open requests
for a specific container.  It is possible that a component (non-user)
has opened a container.

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Everitt, Glenn
Sent: Wednesday, March 14, 2007 8:47 AM
To: Corona development
Subject: RE: [corona-dev] Ref count for container.

...deleted stuff

> */[Glenn] I thought we were only interested in other Users that were 
> active in my Container - since all of the views are within in the 
> context of a container. I'm only interested in users that have the 
> same container open as I do. This approach gives me the ability to NOT

> be available to others in a Containers I don't have open, even though 
> I may be "online"/*
>

[Marcin] You have two computers. You may want to open the same container

twice, have two clients open for the same team member. Then when you 
close one of the containers, the "close" event is sent. With current 
semantic, this would mean you are offline, but you still have one 
instance running. It is not about being online in an other container.

[Glenn]  OK - then do we need to reference count users?  Or should we do
what you suggested earlier and keep track of a ClientID and an
associated User?  That would mean "Close" is for a Container with
associated with a ClientID.  We still need to know if a user is still
available in a particular Container...

So, do we need to define semantics for? 
Client - open, close
User - on, off
Container - open, close
User in a Container - yes, no
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.