Submitted by duncanc on Thu, 05/16/2013 - 14:48
Forums
IceBreak

We have setup an IceBreak server that we use to host several web service programs from.

It appears that when these web services are called, the sessions that they create persist and are re-connected to on the next call to the web service.

It also appears that web service program A and web service program B can use the same session (LDA, library list, etc)

Is there a way we can prevent or control this? Either by forcing each web service program to use a session unique to itself, or by forcing a web service to close the session when it returns?

Thanks,
Craig

Niels Liisberg

Thu, 05/16/2013 - 17:16

Permalink

Hi Craig;

By default all webservices are stateless - so it schould not matter to you that is shares the same session. However, we have some "values added features" to soap so you can controle your sessions. What you need is to provide a unique session id in the SOAP URL - IceBreak seseesions is ISO-timestamps with millisec

So instead of:

   http://myibmi:12345/mySoap.asmx

you client code can add you own unique timestamp in form .CCYYMMDDHHMMSSmmmmmm:

 

   http://myibmi:12345/.20130102010203123456/mySoap.asmx

 

Regards

Niels 

That's perfect Niels, thanks.

While I agree that it shouldn't matter if it's the same session, sometimes (usually just during development) we need to start with a clean session, then it's easier to know what we need to set. This allows us to do that

Thanks again,
Craig