I just need to know if WCF is platform independent like Webservices? Can the functions in WCF be accessed by Java and Php?
Thanks
Yes sure - WCF itself will run on Windows only - but the services it provides can be accessed from any other language / tool.
And using WCF as a client, you can also access any other tool's services, e.g. you can access a webservice written in PHP, Java, etc.
That's the whole point of SOA! :-)
Marc
Yes, WCF is a superset of web services. It can do both platform independent as well as platform dependant communication. You just need to choose one of the wsXXX bindings.
See here for a list of the bindings that WCF supports: http://msdn.microsoft.com/en-us/library/ms730879.aspx
yes if you use standard-compliant binding (any that has WS in the name like WsHttpBinding)
WCF is Web Services - plus a lot more. It replaces the older ASMX service feature.
Related
I need to create client application and server service application, that uses Remote Procedure Calls with windows authentification and impersonation.
Since WCF is not supported in Net Core and gRPC uses http/2, which not supppoted by Windows Authentification are there any alternatives I could use for that?
WCF is a Windows-only framework, while.net Core is cross-platform.
The links below contain some usage and examples that you can refer to.What replaces WCF in .Net Core?
Thanks.
I have found the ServiceWire package to be an excellent replacement for NamedPipes and WCF, especially if you do not need to queue requests or share objects.
While more modern approaches would be preferred, if you already have heavy WCF dependencies or WCF knowledge, you can look into CoreWCF.
If I create a WCF service can it be used by any other system (legacy etc.) that can make use of HTTP GET and POST?
I would like to open up our system with WCF.
Of course yes. WCF provides interoperable bindings like BasicHttpBinding, wsHttpBinding. They can be consumed from other platforms.
have a look at: http://msdn.microsoft.com/en-us/library/ms730017.aspx
I wonder what is the different between Web Services and WCF? Aren´t they the same thing?
Thanks in advance!
I heared about two types of web services.
XML Web Services
WCF Web Services
What is the real difference?
Web services can be built with any number of technologies, while Windows Communication Foundation is specific to .NET. WCF is not specific to communicating via HTTP. It can also work directly over HTTP.
Check out the linked Wikipedia page for more about it.
No, they are not the same thing. While you can certainly replicate the behavior of ASP.net web services in WCF, WCF is a far more fully featured (and complex) platform for developing SOA. It enables to you to take much more control of the messages exchanged between your client and servers, and offers you many more options in regards of protocols and bindings for your endpoints.
Take a look at this article for an overview on some of the differences.
I would like to use a technology that is used for communication between services and several thousands of clients. I came to know of WCF and read a little about it. While it looks attractive and has no interoperability issues, i would like to know about other leading technologies which can give me the same features as WCF ? Are there any open source technologies out there ? Also, which is the most widely used technology? I just want this information before i commit myself to WCF.
EDIT: By alternative to WCF, i mean to say that i am looking for a framework that will help me to implement a webservice in linux or any other platform. For example, the wcf simplifies the process of creating a webservice by the use of hard coded .NET applications. Similarly, i need a tool in linux. I came across mono,but found out that it is not complete and not very reliable.
I also provide an Open Source WCF alternative in ServiceStack A modern, code-first, DTO-driven, WCF replacement web services framework encouraging code and remote best-practices for creating DRY, high-perfomance, scalable REST web services.
There's no XML config, or code-gen and your one clean C# web service is enabled all JSON, XML, SOAP, JSV, CSV, HTML endpoints are enabled out-of-the-box. It includes generic sync/async service clients providing a fast, typed, client/server communication gateway end-to-end.
I don't think there is any .net framework with comparable features. But the core protocols of WCF such as WSDL/SOAP are not Microsoft specific so it's not as if you're tying yourself into a particular protocol, you're just choosing an implementation.
To put it another way if you choose to migrate away from .net in the future then I would say the WCF migration would be one of the easiest parts. But if you stay with .net WCF is almost certainly going to be the best implementation available given the investment Microsoft has in it (Azure is built on WCF for example).
I use the term network services to refer to things such as NNTP, IMAP, POP3... things which have a defined protocol layered on top of TCP/IP.
I'm having a very difficult time figuring out how I can connect to an existing network service using a WCF client. I haven't found any examples other than ones that are basically using C#-ified socket code.
Can anyone refer me to any examples of using WCF to talk to a legacy service as something other than a glorified socket?
Is WCF even appropriate for this type of requirement?
Thanks.
WCF comes with a set of standard bindings, here is a list of the bindings provided in 3.5:
http://msdn.microsoft.com/en-us/library/ms730879.aspx
If you need to use anything else, WCF is probably not the way to go. Even if you could build your own binding, the cost would outweigh the benefit.
If you have a requirement in your project that everything should use WCF, you could build a WCF facade over your sockets code.
Well, the term "WCF" actually means 2 things:
The framework: "ABC" - Address, binding, contract
Actual use of a combination of the above (for example, a WCF webservice using BasicHttpBinding)
There's not built in bindings for the protocols you mentioned, which is why the examples you'll see looks like "glorified sockets" - That's what they are. That's what a binding is: A level of abstraction built on a basic protocol (typically UDP/IP or TCP/IP).
Now, with all this being said, you need to build / borrow / steal / whatever a binding that is usable with your protocol of choice. This might look like you're just injecting sockets into the WCF framework, and honestly, that's just what it is :)... So what's so great about it?
If you managed to implement your binding to-the-specs, you got yourself a very easily substituted component, which will fit into all WCF applications. Whether you want this behaviour or not, is up to you and your requirements :)
Good luck with it.
Well, WCF at its heart is the unified communication engine offering by Microsoft, based on SOAP - it replaces ASMX web services, WSE, .NET Remoting and more.
As such, it's SOAP based and therefore can talk to anything that talks SOAP - which I doubt is the case for POP3 or other services. So I don't think you can write a WCF client for these services, really.
As for writing these services from scratch and exposing them as WCF services - that might work, since basically the WCF service implementation can do anything, and then present itself to the outside world as a SOAP service - could work, question is: what's the benefit?
Marc