How to get large amount of data from a Windows Service

  • Thread starter Thread starter Just_a_fan
  • Start date Start date
J

Just_a_fan

I am thinking about splitting a program I have into a service component
to collect data and a presentation piece to display it. It would
require sending about 40KB of data when a display is needed. I would
rather stay away from an access database and don't really know enough
about SQL and what it would take to go that way, or even if it would
work.

I would like to know what suggestions members have on how to implement a
data transfer like that on request. It would not be every second but
just when the user asked for an update of the graph.

Just don't know where to start researching this. Pointers to a process
I can research would be appreciated. If it takes a database, then so be
it but would like to explore other avenues until that is found to be the
best or only answer.

These two processes will be on the same machine to start with but may be
on separate machines later on. I have heard about named pipes but don't
know how they work yet, either.

Just wondering. It may never happen and is not a commercial project nor
a school assignment. Just something I am using to help learn .NET after
so many years on VB6.

Thanks for any pointers on how to proceed or just not even bother.

Mike
 
(e-mail address removed) wrote in 4ax.com:
I would like to know what suggestions members have on how to implement a
data transfer like that on request. It would not be every second but
just when the user asked for an update of the graph.

..NET remoting or WCF.
 
Definitely .NET Remoting ftw. But make sure you are using the IPC channel
and not a TCP/UDP channel as it could well be blocked by the users firewall.
 
NickP said:
Definitely .NET Remoting ftw. But make sure you are using the IPC
channel and not a TCP/UDP channel as it could well be blocked by the
users firewall.

True, but TCP/UDP will allow remote access :-)

Isn't localhost traffic usually exempt from firewall rules?
 
Well, goodness, looks like I have to really do some reading. I don't
know what ".NET remoting" is and never heard of an "IPC channel" so back
to the books and online helps.

Thanks for the new terms. Will be back in a few years when I decide
what it all means. ;-)

Mike
 
Thanks for the new terms. Will be back in a few years when I decide
what it all means. ;-)

It is not that difficult it will probaly take you a few hours

Personally i would go for WCF with a new to start project

Michel
 
It is not that difficult it will probaly take you a few hours

Personally i would go for WCF with a new to start project

Michel

At this point i'd like to know, i have VB 2005 with .NET 2.0. Do i
have to upgrade to VB 2008 or installing .NET 3.0 is enough to work
with WCF and WPF also?

Thanks
 
There is a Community Technology Preview for VS.NET 2005:

http://www.microsoft.com/downloads/details.aspx?FamilyId=F54F5537-CC86-
4BF5-AE44-F5A1E805680D&displaylang=en

It works "OK".

However, if you don't have 2008 and want to cut down on the learning abit,
Remoting works great in 2005.

Thanks but the link is broken, however which steps do i need to take
to work with WCF having VB 2005 with .NET 2.0 (no SP) currently?
Installation order ? (.NET 3.0 upon .NET 2.0 or any service packs
etc..)
 
Back
Top