Thanks for the reply- it was most helpful. I'm new to web services and I don't know the SOAP protocol very well yet, so I was thinking it could be possible for the web service to automatically generate some sort of session ID and pass it back to the client, perhaps embedded within the SOAP protocol. The client could then pull that ID and use it for any subsequent requests. Both .NET and ColdFusion hide so much of the protocol and inner workings of web services that it makes it tougher to see exactly what's happening, and subsequently what's possible. But anyway, it's clear now that SOAP was not built with that in mind. Maybe in the future...
Anyway, it will be easy for me to do some brute force session management. I could easily send back some unique ID (already storing one in the DB), and just pass it back in with every web service call. This was my fallback plan all along if state preservation could not be done automatically. The downside is that I'll have to restore the state of my CFC on every function call, which creates a great deal more stress for the DB server. Oh well. Thanks again, Kevin -----Original Message----- From: Sean A Corfield [mailto:[EMAIL PROTECTED] Sent: Friday, August 08, 2003 4:01 AM To: CF-Talk Subject: Re: Problem calling CFC from .NET On Thursday, Aug 7, 2003, at 17:12 US/Pacific, kevin ruggiero wrote: > Well, I'm not sure it warranted an "of course not", seeing as how it > did work fine when called from ColdFusion If you call if from CF, it's like a local function call. If you call it as a web service, there's no sense of session management - the calling client could be anything so there is no standard way to maintain a session. Sorry, I thought this was very obvious but I guess I'm making assumptions - no offense intended :( > That would make sense, I just was not aware that CF will not maintain > state on calls to web services. Well, it's more that the *client* isn't maintaining session so each time CF is called, it treats it as a new session (imagine turning off cookies and not being able to add tokens to the URL). > I was hoping that it could maintain state through some mechanism > similar to session management, which I don't believe is unreasonable > to fathom. Normally session management occurs through collaboration between the server and the client. It relies on the client following a protocol, either through cookies being passed back and forth or through URL data. Web Services can be called by a wide variety of clients that know nothing about cookies or URL parameters - so there is nothing for the server to hang on to... Sean A Corfield -- http://www.corfield.org/blog/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
