I have a WCF service running in cloud. How can I make calls to it using Corona?
ISO
Strictly speaking, .NET WCF is an XML based service like any other, so you would just need to implement the network.* library and perform calls like any other webservice would accept.
On the other hand, do you really, really need to cal a WCF? It’s amazingly finicky about it’s acceptance criteria and kinda a mess in it’s formatting. I hate calling it long hand and always bind to it using native VS bindings.
The WCF team did a great job, but when it came to RESTful they screwed it up. Ok, that’s kinda unrelated, but if you have the option, I strongly recommend migrating to a more up to date API, like ASP.NET 5 MVC which part and parcel includes WebAPI.
I totally agree with you in what you say about WCF configuration hell. Been doing that from the beginning of WCF and its tricky every single time to get the endpoints configured.
But I still have the WCF service up and running and need to at least demo using it before we can make decisions about replacing it to something else…
ISO
Of course. In this case, I would use fiddler or postman to inspect the request/response and build a client based on that. There is, of course, no native Lua client built for WCF endpoints, but you only need to handle certain queries for a limited set of scenarios. If you prove that it’s more hassle to use something like WCF than a more current RESTful endpoint, you might convince those above of the benefits of migrating.
Strictly speaking, .NET WCF is an XML based service like any other, so you would just need to implement the network.* library and perform calls like any other webservice would accept.
On the other hand, do you really, really need to cal a WCF? It’s amazingly finicky about it’s acceptance criteria and kinda a mess in it’s formatting. I hate calling it long hand and always bind to it using native VS bindings.
The WCF team did a great job, but when it came to RESTful they screwed it up. Ok, that’s kinda unrelated, but if you have the option, I strongly recommend migrating to a more up to date API, like ASP.NET 5 MVC which part and parcel includes WebAPI.
I totally agree with you in what you say about WCF configuration hell. Been doing that from the beginning of WCF and its tricky every single time to get the endpoints configured.
But I still have the WCF service up and running and need to at least demo using it before we can make decisions about replacing it to something else…
ISO
Of course. In this case, I would use fiddler or postman to inspect the request/response and build a client based on that. There is, of course, no native Lua client built for WCF endpoints, but you only need to handle certain queries for a limited set of scenarios. If you prove that it’s more hassle to use something like WCF than a more current RESTful endpoint, you might convince those above of the benefits of migrating.