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

[Marcin Okraszewski <marcin.okraszewski@xxxxxxxxxxxxxxxx>]

Exactly. I meant client as a piece of software, not user.

Marcin


Everitt, Glenn wrote:
> I guess I don't understand why CC Manager would be different from PC
> Manager.  I thought clientUID was for any client software that might be
> using the Container whether there was a user involved or not.
>
> Glenn
>
> -----Original Message-----
> From: corona-dev-bounces@xxxxxxxxxxx
> [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
> Sent: Wednesday, March 14, 2007 12:42 PM
> To: Corona development
> Subject: RE: [corona-dev] Ref count for container.
>
> CC Manager? - NO.  The ContextContainer has no knowledge of a user.
>
> PC Manager - maybe.  The ProjectContainer does have knowledge of a Team
> as well as user.
>
> -----Original Message-----
> From: corona-dev-bounces@xxxxxxxxxxx
> [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
> Sent: Wednesday, March 14, 2007 11:59 AM
> To: Corona development
> Subject: Re: [corona-dev] Ref count for container.
>
> BTW. What do you think of adding "clientUID" to every CC manager call? 
> Or if the proposal with "client context" is accepted, then the client 
> context for each call?
>
> Marcin
>
>
>
> O'Flynn, Dennis wrote:
>   
> > See my comments within the original email...
> >
> > -----Original Message-----
> > From: corona-dev-bounces@xxxxxxxxxxx 
> > [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin
> >     
> Okraszewski
>   
> > Sent: Tuesday, March 13, 2007 1:05 PM
> > To: Corona development
> > Subject: [corona-dev] Ref count for container.
> >
> > If I'm correct we currently keep container open ref count based on
> >
> > users. I think we should have it based on client ID (Corona UUID).
> >
> > Otherwise user wouldn't be able to open two clients for the same 
> > container.
> >
> > */[O'Flynn, Dennis] +1/*
> >
> > This also mean that open/close event shouldn't indicate user's
> >
> > availability. It just shows that a client opened container. For user,
> >
> > there should be some online/offline events. User goes online when he
> >
> > opens first client. He goes offline, when all clients are closed.
> >
> > */[O'Flynn, Dennis] +1/*
> >
> > This means that also some "keep-alive" message should be sent, to
> >     
> detect
>   
> > crashed clients. Otherwise if a client crashes, the container will
> >     
> never
>   
> > close.
> >
> > */[O'Flynn, Dennis] This should be defined as a RESPOSITORY-DESCRIPTOR
> >     
>
>   
> > to specify some web service as well as the frequency to post a 
> > keep-alive message. It would be nice to limit only sending keep-alive 
> > messages to when the client has not post any other container events./*
> >
> > What do you think? Should I enter a bug for this?
> >
> > */[O'Flynn, Dennis] +1/*
> >
> > Marcin
> >
> > _______________________________________________
> >
> > 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. 
> _______________________________________________
> 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.