|
|
Posted by Susan Baker on 12/19/05 19:07
CJ Llewellyn wrote:
<snip>
>>>
>>>
>>>The same way you'd use C#, Java, Python, Perl or gazzillions of other
>>>programming languages as middle tier layers. Web Services + SOAP
>>>
>>>php has a whole suite of libraries already written for this type of
>>>interoperation.
>>>
>>>http://pear.php.net/package/SOAP
>>>
>>>However as you are aleady using .net at the client end, why not write
>>>the backend in C#?
>>>
>>
>>SOAP is too heavy (and thus WDSL/web services goes out the window too), as
>>I mentioned in a previous post. I want to use sockets (I was expecting
>>someone to suggest using HttpRequest class - or whatever) ...
>
>
> Ask yourself what the advantage of trying to reinvent the wheel is? All
> you'll achive is a greater understanding why standardised protocols are a
> good thing(tm).
>
</snip>
Um, speed. Its a well known and demonstrable fact that SOAP is a
monstrously "heavy" protocol and not really ideal for real time systems.
The benefits of being a standard are crippled by its outrageously
sluggish performance.
> You can of cause use .net's http client and return XML records very much
> the same way that RSS feeds/readers work.
>
No. NO XML PLEASE ...
>
>>It seems no one is even aware that this is possible...
>
>
> Now we didn't say that, it's just not the PC approach.
>
Navigation:
[Reply to this message]
|