conceptual question about webservice vs. webapp

[matthias s]

Hi There,

I'm currently building a webservice using a class library which encapsulates
all business logic and a cache mechanism as well to hold recently used
objects. Lets call this "core.dll". I'm accessing the cache using
HttpContext.Current.Cache within this assembly. My question is, if I now
start build a standard asp.net application using the same core.dll, will
objects placed in the cache duplicate? Say, core.dll has a NewsItem object.
My user requests this object through the webservice method GetNews().
Core.dll instanciates the object and stores it in the Cache. The next time
someone coming over the public website requests the news.aspx, is the object
retrieved from cache (because this is a different application) or will be
stored in a "different" cache?

If this is the case, can I build my webapp with my aspx pages and just have
an myservice.asmx service as well in the same project?

Thanks for any help!

[John Saunders [MVP]]

"matthias s" <postamt__add__kieferfrost__dodd__dewrote in message
news:eh**************@TK2MSFTNGP02.phx.gbl...

Hi There,

I'm currently building a webservice using a class library which
encapsulates all business logic and a cache mechanism as well to hold
recently used objects. Lets call this "core.dll". I'm accessing the cache
using HttpContext.Current.Cache within this assembly. My question is, if I
now start build a standard asp.net application using the same core.dll,
will objects placed in the cache duplicate? Say, core.dll has a NewsItem
object. My user requests this object through the webservice method
GetNews(). Core.dll instanciates the object and stores it in the Cache.
The next time someone coming over the public website requests the
news.aspx, is the object retrieved from cache (because this is a different
application) or will be stored in a "different" cache?

If this is the case, can I build my webapp with my aspx pages and just
have an myservice.asmx service as well in the same project?

There will be one instance of the Cache per web application. If you keep the
web site and web service in the same web application, then they will share
the Cache.
--
John Saunders [MVP]

[matthias s]

thanks john!

kind regards, matthias
"John Saunders [MVP]" <john.saunders at trizetto.comschrieb im Newsbeitrag
news:eV****************@TK2MSFTNGP04.phx.gbl...

"matthias s" <postamt__add__kieferfrost__dodd__dewrote in message
news:eh**************@TK2MSFTNGP02.phx.gbl...

>Hi There,

I'm currently building a webservice using a class library which
encapsulates all business logic and a cache mechanism as well to hold
recently used objects. Lets call this "core.dll". I'm accessing the cache
using HttpContext.Current.Cache within this assembly. My question is, if
I now start build a standard asp.net application using the same core.dll,
will objects placed in the cache duplicate? Say, core.dll has a NewsItem
object. My user requests this object through the webservice method
GetNews(). Core.dll instanciates the object and stores it in the Cache.
The next time someone coming over the public website requests the
news.aspx, is the object retrieved from cache (because this is a
different application) or will be stored in a "different" cache?

If this is the case, can I build my webapp with my aspx pages and just
have an myservice.asmx service as well in the same project?

There will be one instance of the Cache per web application. If you keep
the web site and web service in the same web application, then they will
share the Cache.
--
John Saunders [MVP]