Calling External Web service in .Net

Question

1.00/5 (1 vote)

See more:

Hi,,

I am started working on web service recently. and facing some problems while working with it.

1. If Web service is on Remote Ftp then how we can consume / use it?
2. Does FTP supports SOAP protocol?
3. WCFservice and web service which is better?
4. Can we call external web service from within a web service?

Thanks.

Posted 19-Jan-12 23:59pm

comred

Add a Solution

1 solution

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2012-01-20T08:04:00

Please see my answers:

The question is not quite clear. What is "service is on Remote FTP"? The Web service itself is based on HTTP, a protocol on the same Application Level as FTP (please see the references below). If you simply mean using FTP for deployment or support of your Web service code and data, this question is unrelated to the service itself; it totally depends on what your provider's settings or on your own settings on the related hosts including the one running HTTP server.
No. SOAP protocol is the protocol of the Application Level, please see:
http://en.wikipedia.org/wiki/Application_Layer[^],
http://en.wikipedia.org/wiki/SOAP[^].

FTP is on the application level, too. Please see http://en.wikipedia.org/wiki/FTP[^].

There for, the problem is not that FTP cannot "implement" SOAP, the problem is that the question does not make certain sense. What would it be? Just having some files served by FTP (this is what FTP does, nothing else; FTP is just like a kind of a file system, remotely accessed) in the SOAP format? This is not what could be called a protocol.
This is yet another example of things which can not compare. Microsoft maintains that for new development everyone should switch to WCF. I agree as soon as you can use only CLR (.NET but can also be Mono, http://en.wikipedia.org/wiki/Mono_%28software%29[^]). So, it you use just .NET and Mono, you can create a distributed multi-platform (because Mono implements WCF and supports many platfroms including Windows, Linux, Max OS X, Android and other portable systems and more) applications much easier, with much better flexibility and maintainability and less overhead than with Web services.

Nevertheless, there are legacy systems and situation when having .NET or Mono is not an option. In this case, you are bound to Web services which are way more widespread right now.
Sure, why not? Perhaps in many case you need to be sure that using the external Web service is fast enough to keep your calling service responsive enough.

That's it. Thank you for attention.

—SA