<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Comments for Managing sessions with Delphi 6 Web services (updated)</title>
<link rel="alternate" type="text/plain" href="http://dn.codegear.com/article/27575" title="Managing sessions with Delphi 6 Web services (updated)" />
<link rel="self" type="application/atom+xml" href="http://dn.codegear.com/article/27575/feed" title="Comments for Managing sessions with Delphi 6 Web services (updated)" />
<id>http://dn.codegear.com/article/27575</id>
<updated>2008-07-05T13:06:21-07:00</updated>
<entry>
<title>Managing Session and Authentication in Delphi 6 Web Services</title>
<author>
<name>Marc D#rst</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=33795</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=33795</id>
<updated>2002-12-24T02:55:12-08:00</updated>
<published>2002-12-24T02:55:12-08:00</published>
<summary>Managing Session and Authentication in Delphi 6 Web Services</summary>
<content>Hi folks,Nice article. I'm just wondering if there as any paper or something like this which explains the state-/session-behaviour of webservices in a little more details?For example: when one create an instance of a webservice-class, will it keep alive on the server until the object gets freed from the client (incl. member-variables etc.)? I'm thinking of webservices implemented as CGI's which get's fired for every request. Does the VCL store/reload such object-state/-data??Any hint would be great ;-)Cheers,Marc</content>
</entry>
<entry>
<title>re: Thread-unsafe code in GetSession Data?</title>
<author>
<name>Daniel Polistchuck</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=29686</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=29686</id>
<updated>2001-08-19T07:54:52-07:00</updated>
<published>2001-08-19T07:54:52-07:00</published>
<summary>re: Thread-unsafe code in GetSession Data?</summary>
<content>Hallvard,You are 100% correct, I think I already updated this code in my codecentral submission.Thanks,Daniel</content>
</entry>
<entry>
<title>Thread-unsafe code in GetSession Data?</title>
<author>
<name>Hallvard Vassbotn</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=29645</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=29645</id>
<updated>2001-08-15T06:57:13-07:00</updated>
<published>2001-08-15T06:57:13-07:00</published>
<summary>Thread-unsafe code in GetSession Data?</summary>
<content>Nice article. However it looks like this code is not thread-safe:function TAuthenticator.GetSessionData(  const SessionHandle: String): String;begin  Result := '';  if not LocateSession(SessionHandle) then    Exit;  Result := wmAuthServer.cdsSessions.FieldByName ('SessionData').AsString;end;The LocateSession function will use the critical section correctly, but then you leave the critical section, so another thread might change the location of the CDS before you extract the field contents.Wrap this code by another try..finally section that enters and leaves the critical section, and it should be safe./Hallvard</content>
</entry>
<entry>
<title>Comments are welcome!</title>
<author>
<name>Daniel Polistchuck</name>
<uri>http://threads.codegear.com/threads/threads.exe/userall?commentid=29596</uri>
</author>
<id>http://threads.codegear.com/threads/threads.exe/view?commentid=29596</id>
<updated>2001-08-09T05:44:26-07:00</updated>
<published>2001-08-09T05:44:26-07:00</published>
<summary>Comments are welcome!</summary>
<content>Please flaaame me :) (But don't scorch me :P )</content>
</entry>
</feed>
