Eclipse Community Forums: EMF » [CDO] explicit session closing.

Help

Home

Home » Modeling » EMF » [CDO] explicit session closing.

Show: Today's Messages :: Show Polls :: Message Navigator

[CDO] explicit session closing. [message #686794]

Thu, 19 May 2011 10:44

Christophe Bouhier

Messages: 937
Registered: July 2009

Senior Member

Hi, I noticed, if either explicitly closing a CDO session, or not
closing it, will lead to a new Session ID being assigned on the next
openSession().

(SessionID being visible by calling CDOSession instance toString()).

Is this the expected behaviour? Does it mean the CDOSession is
maintained on the server side after close, or perhaps the sessionID's
are assigned round-robin?

Thx Christophe

Report message to a moderator

Re: [CDO] explicit session closing. [message #686795 is a reply to message #686794]

Thu, 19 May 2011 10:57

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

Am 19.05.2011 12:44, schrieb Christophe Bouhier:
> Hi, I noticed, if either explicitly closing a CDO session, or not closing it, will lead to a new Session ID being assigned on the next openSession().
>
> (SessionID being visible by calling CDOSession instance toString()).
Or by calling org.eclipse.emf.cdo.common.CDOCommonSession.getSessionID() ;-)

>
> Is this the expected behaviour? Does it mean the CDOSession is maintained on the server side after close, or perhaps the sessionID's are assigned round-robin?
Yes, round-robin over the set of positive 4 byte integers, with starting at 1 for each repository activation :P

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator

Re: [CDO] explicit session closing. [message #686796 is a reply to message #686795]

Thu, 19 May 2011 10:59

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

Please note that, with the advent of the CDORemoteSessionManager, clients can get aware of other sessions to the same repository and communicate with them asynchronously. Because of possible race conditions we chose not to reuse session IDs while a repository is active.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Am 19.05.2011 12:57, schrieb Eike Stepper:
> Am 19.05.2011 12:44, schrieb Christophe Bouhier:
>> Hi, I noticed, if either explicitly closing a CDO session, or not closing it, will lead to a new Session ID being assigned on the next openSession().
>>
>> (SessionID being visible by calling CDOSession instance toString()).
> Or by calling org.eclipse.emf.cdo.common.CDOCommonSession.getSessionID() ;-)
>
>>
>> Is this the expected behaviour? Does it mean the CDOSession is maintained on the server side after close, or perhaps the sessionID's are assigned round-robin?
> Yes, round-robin over the set of positive 4 byte integers, with starting at 1 for each repository activation :P
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator

Re: [CDO] explicit session closing. [message #686798 is a reply to message #686796]

Thu, 19 May 2011 11:31

Christophe Bouhier

Messages: 937
Registered: July 2009

Senior Member

On 19-05-11 12:59, Eike Stepper wrote:
> Please note that, with the advent of the CDORemoteSessionManager,
> clients can get aware of other sessions to the same repository and
> communicate with them asynchronously. Because of possible race
> conditions we chose not to reuse session IDs while a repository is active.

Thanks Eike!
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
>
>
> Am 19.05.2011 12:57, schrieb Eike Stepper:
>> Am 19.05.2011 12:44, schrieb Christophe Bouhier:
>>> Hi, I noticed, if either explicitly closing a CDO session, or not
>>> closing it, will lead to a new Session ID being assigned on the next
>>> openSession().
>>>
>>> (SessionID being visible by calling CDOSession instance toString()).
>> Or by calling
>> org.eclipse.emf.cdo.common.CDOCommonSession.getSessionID() ;-)
>>
>>>
>>> Is this the expected behaviour? Does it mean the CDOSession is
>>> maintained on the server side after close, or perhaps the sessionID's
>>> are assigned round-robin?
>> Yes, round-robin over the set of positive 4 byte integers, with
>> starting at 1 for each repository activation :P
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://www.esc-net.de
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>>
>>

Report message to a moderator