How to have a win2k service and a web service use a single static cache (shared)

[noah]

Hi,
I'm in the middle of writing a multi-user system with very
critical timing issues. I've already implemented a cache and an API to
access it (with appropriate locking for multithreaded access). This
shared cache is critical / the primary function of the system.

At the core of this system there is a cache of objects that can be
modified by anyone, and a windows service (thread) that will run
operations with the cached objects on regular intervals.

I need a way to allow a web services host (local machine asp.net
WS) to access this single/core cache thru the local API and am
thinking that if I simply implement a web services layer it will run
in its own .NET runtime and in that runtime have a seperate
cache-singleton. Is this correct? As I understand it (on shaky info)
different .NET apps will run in their own runtimes.

Please reply on the forum and let me know if my assumptions in the
last paragraph are true. If they're false, I'm home free (all .NET
apps on a machine share a common runtime). If they're true, I'll need
a way - possibly .NET remoting, to identify and access the .NET
runtime containing my singleton cache running in the service thread.

Thanks in advance for your help -
Noah

[Cor Ligthert]

Hi Noah,

A long message and impossible to anser in a newsgroup completly in my
opinion however some statements

With Visual .studio Net you can create your own applications (Dll) wich is
are webapplications. Those share all resources between the users from a
specific webapplication (I try to tell it in a few words), while you can
split the users actions in sessions.

You can see Net as a runtime, however than Windows Server is also a runtime.
Net is a more complex instrument than a runtimer, which only gives standard
instructions to the OP.

Net manages also things as memory to keep up the system when you are not
using things as API's

I get the idea, you never did look deep at Visual.Studio Net, have a look at
the benefits from it. I get the idea that you can improve your application
very much with it.

Just my thought,

Cor

[Cor Ligthert]

Hi Noah,

A long message and impossible to anser in a newsgroup completly in my
opinion however some statements

With Visual .studio Net you can create your own applications (Dll) wich is
are webapplications. Those share all resources between the users from a
specific webapplication (I try to tell it in a few words), while you can
split the users actions in sessions.

You can see Net as a runtime, however than Windows Server is also a runtime.
Net is a more complex instrument than a runtimer, which only gives standard
instructions to the OP.

Net manages also things as memory to keep up the system when you are not
using things as API's

I get the idea, you never did look deep at Visual.Studio Net, have a look at
the benefits from it. I get the idea that you can improve your application
very much with it.

Just my thought,

Cor

[noah]

Maybe I can clarify,
I'm not writing a typical multi-user program based on web
services. I'm trying to build a system that, at its' core, has a
windows service running and doing certain tasks periodically. The
tasks are cached in memory at this service, as performance and
concurrency issues are critical.

Now, a requirement for this app, is that users/systems across the
enterprise can in real-time, without any delay,
monitor/edit/add/delete tasks from the centralized cache. The current
proposed solution is to have a web-service running on the same server
as the service with the cache. I'm not worried about web user sessions
- the web services (API methods) are stateless.

The main concern: How can I have a web service running with IIS
to access the single static cache in my windows service? As far as I
know, it does matter if these are in different runtimes, as they would
each have their own instances of the static cache.

Thanks,
Noah

[noah]

Maybe I can clarify,
I'm not writing a typical multi-user program based on web
services. I'm trying to build a system that, at its' core, has a
windows service running and doing certain tasks periodically. The
tasks are cached in memory at this service, as performance and
concurrency issues are critical.

Now, a requirement for this app, is that users/systems across the
enterprise can in real-time, without any delay,
monitor/edit/add/delete tasks from the centralized cache. The current
proposed solution is to have a web-service running on the same server
as the service with the cache. I'm not worried about web user sessions
- the web services (API methods) are stateless.

The main concern: How can I have a web service running with IIS
to access the single static cache in my windows service? As far as I
know, it does matter if these are in different runtimes, as they would
each have their own instances of the static cache.

Thanks,
Noah

[Cor Ligthert]

Hi Noah,

Seperate what I said before I think you have to look for on
mdsn.microsoft.com with the keyword "remoting", than you will find a lot of
articles, helps and whatever that depends your question.

I hope this helps?

Cor

[Cor Ligthert]

Hi Noah,

Seperate what I said before I think you have to look for on
mdsn.microsoft.com with the keyword "remoting", than you will find a lot of
articles, helps and whatever that depends your question.

I hope this helps?

Cor