You'll have to use static variables or maintain an index / collection
that's shared in your web service call. Start by thinking what objects
are created and then destroyed by the SOAP / web service calls, independent
of other calls.
Maybe you would want to store this variable in the WebService.Context
object (of type System.Web.HttpContext) which is created for the request.
Check out the "Items" collection member variable.
--
CharlieN
DevDiv
This posting is provided "AS IS" with no warranties, and confers no rights.
Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
--------------------
> From: poul_lund_joergensen@hotmail.com (Poul Lund J?rgensen)
> Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
[quoted text clipped - 7 lines]
> Content-Transfer-Encoding: 8bit
> X-Trace: posting.google.com 1085745501 1877 127.0.0.1 (28 May 2004
11:58:21 GMT)
> X-Complaints-To: groups-abuse@google.com
> NNTP-Posting-Date: Fri, 28 May 2004 11:58:21 +0000 (UTC)
> Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!news-out.cwi
x.com!newsfeed.cwix.com!prodigy.com!prodigy.com!news.glorb.com!postnews1.goo
gle.com!not-for-mail
> Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:24047
> X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 17 lines]
> best regards
> Poul Lund J?rgensen