Well, I'm not sure it warranted an "of course not", seeing as how it did work fine when called from ColdFusion (I assume CF does not access it through the "web service" channels, even though it's stated to be a remote function). That would make sense, I just was not aware that CF will not maintain state on calls to web services. I was hoping that it could maintain state through some mechanism similar to session management, which I don't believe is unreasonable to fathom.
Kevin >On Thursday, Aug 7, 2003, at 11:57 US/Pacific, Ruggiero, Kevin D. wrote: >> The problem with doing this from ASP.NET is that the CFC does not >> appear to >> maintain its state between the function calls. > >Of course not - Web Services are effectively stateless - you are >creating a new instance for every Web Service call. > >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 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
