By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,851 Members | 1,118 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,851 IT Pros & Developers. It's quick & easy.

memory sharing between application solutions

P: n/a
I am having an issue to where I need to share memory between an ASP.Net
solution and a VB.Net solution. I have several large arrays and
collections that are updated every half second. The data is only
about 30k, but saving to a file or stringing into text uses too much
processor time. I would appreciate any suggestions, Thank you
Dec 9 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Mkillian,

After the 60's there have not been much operatingsystems (which where not
before that time), which makes it you able to share memory.

What you can do is give informations from one application to another. The
words to search for that on MSDN are pipes (what you probably need) or
remoting when it is about a multi computer environment.

Probably do you need a windowservice to handle your problem.

I hope this helps,

Cor
Dec 10 '05 #2

P: n/a
I understand that the OS will not directly share out memory as it breaks up
the process memory into virtual memory with a 2/4 gig limit. I suppose I am
looking for a solution somewhat similiar to an activex exe where there is
some process in between each .NET solution that will have a singleton
approach. I'm just hoping I do not have to use VB6 to link my .NET solutions.

"Cor Ligthert [MVP]" wrote:
Mkillian,

After the 60's there have not been much operatingsystems (which where not
before that time), which makes it you able to share memory.

What you can do is give informations from one application to another. The
words to search for that on MSDN are pipes (what you probably need) or
remoting when it is about a multi computer environment.

Probably do you need a windowservice to handle your problem.

I hope this helps,

Cor

Dec 12 '05 #3

P: n/a
Mkillian,

Why do you want to emulate a method from the 60's while there are so much
new methods made after that.

Just my thought,

Cor
"mk******@osmose.com.nospam"
<mk*********************@discussions.microsoft.com > schreef in bericht .
I understand that the OS will not directly share out memory as it breaks up
the process memory into virtual memory with a 2/4 gig limit. I suppose I
am
looking for a solution somewhat similiar to an activex exe where there is
some process in between each .NET solution that will have a singleton
approach. I'm just hoping I do not have to use VB6 to link my .NET
solutions.

"Cor Ligthert [MVP]" wrote:
Mkillian,

After the 60's there have not been much operatingsystems (which where not
before that time), which makes it you able to share memory.

What you can do is give informations from one application to another. The
words to search for that on MSDN are pipes (what you probably need) or
remoting when it is about a multi computer environment.

Probably do you need a windowservice to handle your problem.

I hope this helps,

Cor

Dec 12 '05 #4

P: n/a
I've looked into pipes and found that I cannot use pipes for our application.
These applications are not on servers, which are required for a server
pipe.
http://msdn.microsoft.com/library/de...lnamedpipe.asp

I was rather hoping that there would be a function in which I could just
pass a pointer to another process with public arrays. I have 3 boolean
arrays of 3000 x 4 dimensions. 4 short arrays of 3000 x3 and 4 double
arrays of 2000x7. It just seems like there should be a better method than
pipes aside from the whole server issue.

I would have to stuff 8 bits per byte, across 12 dimensions...for the
booleans. Reverse that on the way out. Same flip process on the values >
256.

..NET has included the Memory Marshal object where within a process, memory
can be re-allocated and create a duplicate of memory from pointer A - B.

I suppose I am hoping for a solution that will be faster than doing any
bitwise compression because all of these values have a need to be read by
BOTH solutions every second....24/7 hopefully for years. This system has no
media storage for saving a file other than RAM.

I hope that explains more to what I am looking for, and why.

Thanks for your advice Cor
"Cor Ligthert [MVP]" wrote:
Mkillian,

Why do you want to emulate a method from the 60's while there are so much
new methods made after that.

Just my thought,

Cor
"mk******@osmose.com.nospam"
<mk*********************@discussions.microsoft.com > schreef in bericht .
I understand that the OS will not directly share out memory as it breaks up
the process memory into virtual memory with a 2/4 gig limit. I suppose I
am
looking for a solution somewhat similiar to an activex exe where there is
some process in between each .NET solution that will have a singleton
approach. I'm just hoping I do not have to use VB6 to link my .NET
solutions.

"Cor Ligthert [MVP]" wrote:
Mkillian,

After the 60's there have not been much operatingsystems (which where not
before that time), which makes it you able to share memory.

What you can do is give informations from one application to another. The
words to search for that on MSDN are pipes (what you probably need) or
remoting when it is about a multi computer environment.

Probably do you need a windowservice to handle your problem.

I hope this helps,

Cor


Dec 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.