instantiating an object from a web service vs instantiating an object from a regular class

Question

I have a very basic web service:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Services;

namespace          


        

Answer 1

Becaue on the server side the class is created and disposed with EVERY call you make from the client... your client is just a "proxy" and doesn't correspond directly to an instance on the server side...

You can either make myInt static or make the server side service class a Singleton... both options would mean that myIntis shared across ALL client... or you could implement some session management to achieve a client-specific myInt... using WCF for the server side seems IMHO the best solution - it comes with configurable options for singleton, session management etc.

EDIT - as per comments:

With WCF you can have .NET-clients with session management which in turn allows you to have different (client-specific) values for myInt...

Answer 2

Services created through the older .asmx technology are not singleton instances. This means that each call you make to the server instantiates a new instance of the service each time. Two real solutions, either use static variables (eugh....), or switch to using WCF.

Answer 3

webservice instance is destroyed at the end of each method call, so that's why you always get the same result. You need some way to persist that value.