If your aim is writing web services, another option is
the MS SOAP toolkit, both for calling and building web services.
Its very easy to use, and you can use almost any current windows
version of delphi, since its just involves writing or calling some basic COM
components. No waiting for Delphi.NET or paying through the nose for an
"enterprise" version of Delphi.
I think the current hype for SOAP based web services is
getting a little too much. People are placing it everywhere in their
architectures, but its only really suited for loosely coupled web
applications. SOAP is just a simple, ineffecient protocol for calling
simple functions, good at what it does, but as it currently stands, it shouldnt
replace DCOM IMHO.
|
- Re: [DUG]: .net vs websnap Tracey Maule
- Re: [DUG]: .net vs websnap Neven MacEwan
- Re: [DUG]: .net vs websnap Tracey Maule
- Re: [DUG]: .net vs websnap Neven MacEwan
- Re: [DUG]: .net vs websnap Tracey Maule
- Re: [DUG]: .net vs websnap Neven MacEwan
- RE: Re: [DUG]: .net vs websnap Peter Speden
- Re: Re: [DUG]: .net vs websnap Tracey Maule
- RE: Re: Re: [DUG]: .net vs websnap Wilfred Verkley
- RE: Re: Re: [DUG]: .net vs websnap Peter Speden
- RE: Re: Re: [DUG]: .net vs websnap Sandeep Chandra
- [DUG]: ClassNotFound Exception for no appare... David Smith
- Re: [DUG]: ClassNotFound Exception for n... Nello Sestini
- RE: [DUG]: ClassNotFound Exception ... David Smith
- RE: Re: Re: [DUG]: .net vs websnap Alan Rose