RAPWare Easy SOAP vs. DSOAP
Kongthap Thammachat
* I'm using Delphi 5
** I would like to implement a company's web service using Delphi5 + 3rd
party component
*** I wish, the web service should later be able to be consumed by windows
applications written with Delphi and intranet web application written using
asp.net technology.
Thanks for all advices.
Kongthap
G. Allen Casteran
We looked briefly at both products and chose DSOAP.
1) Lower cost
2) We new Alesandro
3) Seemed to be more clear about how to build the objects.
Actual experience...
DSoap is a good product. At present you have to use DSoap for both your server
and your client components. Building a universal server is presently not
available. Alesandro's documentation leaves a lot to be desired, especially in
the areas of "something did not work right".. Getting the initial soap service
installed and runnnig wa a real pain, mostly because Alesandro built and tested
under Win2K, and we were building on Win2K and installing on NT40. IIS 4 and
IIS 5 have a significant difference in their configurations. (one of the
settings is completely reversed between the versions <argh!!!>). There are
several system libs that need to be installed on the client to run SOAP. This
is fairly germane to ANY SOAP implementation. In particular we needed to make
sure the MSXML3 libs were installed.
All in all I would say it is a good product and am still pleased that we chose
DSOAP.
Alesandro is going to release an update soon which will provide a universal
server, choice of ISAPI or stand-alone exe deployment model, and blazing speed
improvements.
Allen.
Steve Garland
several system libs that need to be installed on the client to run SOAP.
This
is fairly germane to ANY SOAP implementation
Not to ASTA SOAP as there is NO COM requirements as ASTA SOAP has a native
XML parser for Kylix and Windows. No deployment issues. No proxy issues.
Servers build using ISAPI or Kylix DSO or a standalone HTTP server using the
AstaIO cross platform sockets.
We hope to have a full release in August for starting at $99.
http://www.astatech.com/announcements/soap.asp
www.astatech.com/files/examples/AstaAmazonSoapClient.exe for an example
using an Asta SOAP client connecting to an Amazon Soap Service to lookup
books by authors.
No Runtime fees. No dependence on ASTA 3 or AstaIO (although ASTA 3 and
AstaIO integration is available and ASTA SOAP comes as part of ASTA 3 and
AstaIO licenses)
C#, MSIE, Delphi 6, PHP, VB and more client examples coming.
--
Steve Garland sgar...@astatech.com
SkyWireMeeting - Show Any Desktop to any number Browser Clients in real time
Asta LiveVideo - Win32 and WinCE Secure Streaming Video- add Voice with
Asta VoIP
ASTA Technology Group http://www.astatech.com http://www.astawireless.com
Alessandro Federici
news:3d4660a4_2@dnews...
> Please anyone here give me a brief comparison between these 2 products.
DSOAP main advantages over the other toolkits are the following:
1) Compression of XML data
DSOAP uses a unique approach for compressing XML packets which can improve
performances up to 10 times or more when you are dealing with medium/large
packets of data (let's say 40/80 kbs or a dataset with 50 records for
instance). DSOAP servers are able to understand if the client requesting the
data is a DSOAP one (=can use compression) or a regular one (Java, .Net,
Borland Delphi's) which should be treated in a standard way. While choosing
to use compression is still your choice, this makes it possible to create
web services that can be used in all those situations where ASTA is used for
instance without any performance drawback. No other SOAP toolkit offers this
and trust me, makes all the difference of the world.
2) Maximization of the Windows platform by using COM underneat
While COM is in my opinion a great thing to use underneat any scalable nTier
system running on Windows, it might also be a little problem if you are not
used to work with it. Many businesses use COM when creating the Windows
middle tier. The reason is because they want to write systems that are easy
to scale and monitor and at the same time open to other systems in a
standard way (COM). The probelm is enabling those services to be used
outside Windows and over the web. This is where SOAP comes in of course. So
why to reinvent the wheel and force the user to rethink their code in order
to remote an existing remotable object?
To recap, if you have an existing COM object you are pretty much done. In
order to make it a web service you don't have to code a single line of code
in order to remote it through SOAP. It's all done externally, compression
included. You see the advantage over any other toolkit (assuming you use/are
confortable with COM).
DSOAP is a solid product and it has been used since before Delphi 6's web
service framework.
I am currently working on a totally new messaging framework called
RemObjects now. It was originally supposed to be DSOAP version 3 but since
COM is no longer required (you can still use if you want anyhow) and SOAP is
just one of the protocols you can use, I decided to go for a new name. If
you want more information and see a screenshot log on my DSOAP newsgroup at
news://news.astatech.com/astatech.dsoap
If decide to buy DSOAP now the upgrade to RemObjects will be free.
If you have any other question please feel free to contact me directly or
post on the DSOAP newsgroup.
More about DSOAP at
http://www.msdelphi.com/Articles/Products/DSOAP21/DSOAP21Intro.htm
--
Alessandro Federici
-System Architect
-Borland Certified Consultant
-DXSquad Team Member
Homepage: www.msdelphi.com (home of the DSOAP Toolkit)
EMail: al...@msdelphi.com
"If Java had true garbage collection, most programs would delete themselves
upon execution." (Robert Sewell)
"Freedom does not mean that you get everything you want any way you want
it." (JQP)
*** Prevent the impending death of Internet radio! Log on
http://www.saveinternetradio.org ***
Alessandro Federici
news:3d471581_1@dnews...
> "Kongthap Thammachat" <je...@hotmail.com> wrote in message
> news:3d4660a4_2@dnews...
> > Please anyone here give me a brief comparison between these 2 products.
This is a note one of my DSOAP customers sent me.
"Alessandro Federici's DSOAP toolkit has made the whole process of moving
from client-server to a 3 tier model a much simpler task. Availability of
the source code and excellent support from Alessandro himself has allowed us
to fine tune the DSOAP components to suit our business needs. Performance is
good and features such as the inbuilt SOAP message compression alone have
decreased the message size by 80% [Clive Carey - Emis]"
Brian Moelk
You are not referring to DCOM, but rather plain old COM correct? IMO DCOM
sucks; can't set timeouts, just try to get things to fail gracefully when
you pull network cables out in the middle of calls.
--
Brian Moelk
bmoe...@SPAMbrainendeavorFOR.MEcom
http://www.brainendeavor.com
Alessandro Federici
news:3d4768d5_1@dnews...
> > 2) Maximization of the Windows platform by using COM underneat
>
> You are not referring to DCOM, but rather plain old COM correct?
Yes, correct.