Network services

Question

0.00/5 (No votes)

See more:

Is there any possibilty to implement a couple of methods on a global server so that I could use them from any application in the network or from the web? These methods will get parameters and return results. I wish that these methods (or services..?) work like a windows service - run in the background as long as Windows is running, or they can be started manually when required. It is possible to make that kind of service visible in network?
How can I do that and what tools will I need to use?

Thank you!

Posted 20-Dec-10 23:54pm

mnd017

Updated 20-Dec-10 23:58pm

Manfred Rudolf Bihy

v2

Add a Solution

3 solutions

Solution 2

Well, you could also use WebService.
It will be easier to setup.

Posted 21-Dec-10 1:28am

Jefis

Solution 1

Yeah, you can set up a windows service that allows connections via TCP/IP sockets, WCF, or whatever. At that point, you can make the service do anything you want on the remote machine.

Posted 20-Dec-10 23:57pm

#realJSOP

Updated 20-Dec-10 23:58pm

v2

Comments

Manfred Rudolf Bihy 21-Dec-10 11:36am

Moved to comment of OP's behalf:
Hi, thx for your replies. I'm just learning but I don't want the easiest way. What is the best way to implement such a system. Web service or windows service?

This service (or method in this service) will send and receive big amount of data. I thought, maybe Windows Service, but how can I host them ?

Could you suggest me, an architecture for that kind of system (in C#)?

Thank you for helping me

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dylan Morley · Accepted Answer · 2010-12-21T05:31:00

It depends what you want to do with the service

You could expose functionality in a windows service and consume that from your clients using binary remoting over TCP. This is something we use on an older system, but it's been very successful & performance is excellent.

This would be fine for 'internal users on a LAN', but you wouldn't expose this to the internet

If you want your functionality to be consumed by any client, anywhere - then a web service is probably the way to go

This article is pretty good and compares the different approaches. (It's dated now - 2003 - but the concepts are still valid even if they've been superseded by WCF etc)

http://www.developer.com/net/net/article.php/2201701/NET-Remoting-Versus-Web-Services.htm[^]

I quite like this diagram at the end

http://www.developer.com/img/articles/2003/05/06/Thiru/Remote4.jpg[^]

Notice how both the internal and 'internet users' consume the same code, it's just it's exposed to internet users by wrapping in a web service