Shared memory?

[Jon Davis]

I really don't like the speed bottleneck of SOAP. Is it possible to have
shared memory, without using networking calls, within .NET?

It seems like even though protected memory was a godsend for memory leaks
and unauthorized access type stuff, we should at least be given a leash to
take the dog out for a walk for a while.

Jon

 

[Simon Smith]

I really don't like the speed bottleneck of SOAP. Is it possible to have
shared memory, without using networking calls, within .NET?

It seems like even though protected memory was a godsend for memory leaks
and unauthorized access type stuff, we should at least be given a leash to
take the dog out for a walk for a while.

Jon

Shere was am implementation of a shared memory file floating around, as
I recall. Unfortunately I no longer have it and can't remember where I
got it from. Try the gotdotnet or dornet247 sites and a google search.


Sorry not to be more helpful....

Of course, you could do it yourself with DLLImport etc, so you can take
the dog for a walk if you know how.

 

[Richard A. Lowe]

There is a MemoryMappedFile class in the Caching Application Block. I'm
trying to use it at the moment (without much luck!)

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/CachingBlock.asp

 

[Jon Davis]

I was thinking more for desktop applications than services. The Caching
Application Block is geared for services, is it not?

Jon

 

[Jon Davis]

So you're saying just linking to an unmanaged C++ DLLs using p/invoke to do
this is a plausible solution?

Jon

 

[Richard A. Lowe]

I suppose they are, but does it matter? You can either use the classes as
the Cache app block uses them or rip out the calls to the Win32 API and use
them to suit your needs. The app block already implements what Simon was
suggesting, so presumably it is an example of "Standards and Practices" in
how to do so, since that's the area of Microsoft responsible for these
application blocks.

Richard

 

[Sunny]

Hi Jon,

this is not free, but it is not expensive as well and they have a trial
version which is not very limited.

These guys have shared memory remoting channels:

www.genuinechannels.com

Sunny

 

[Simon Smith]

So you're saying just linking to an unmanaged C++ DLLs using p/invoke to do
this is a plausible solution?

Jon

It's not for script-kiddies, that's true. But otherwise - if there's no
other way to do it and it must be done - yes, definitely, it's plausible.
Easy is a different matter.

 

[Eugene Mayevski [SecureBlackbox]]

I really don't like the speed bottleneck of SOAP. Is it possible to have
shared memory, without using networking calls, within .NET?

You can check MsgConnect (http://www.msgconnect.com/) which has an MMF
transport in .NET edition too. MsgConnect will let you exchange messages
between applications (not necessarily .NET, but also Windows, Unix,
PDAs) both on the same computer and across network.