About SOAPClient.com

About SoapClient.com
General Information SoapClient.com is a resource center for SOAP developers. We provide product information, SOAP tools, and SOAP services such as web search and data access. You can reach us at: info@sqldata.com. Technical Information The site is powered by SQLData SOAP server with the following key components: SOAP/HTTP client: The client is compatible with almost all well-known SOAP implementations. It provides direct access to other web services using web browser. WSDL/SDL/WSML Parser: The component parses and validates service description files of different kinds. It uses SAX 2.0 XML parser as basis. SOAP Security: The component performs XML encryption and XML Signature operations, and secures sensitive data inside SOAP messages. SOAP Transport: The component provides extensible wiring methods for SOAP messages. Currently supported transports include HTTP, HTTPS, SMTP, and MSMQ. SRL Processor: This is the Service Request Language processor, which is the key part of SQLData Integration Server. SRL is a much higher protocol than SOAP. It allows direct access to all HTTP services (SOAP or non-SOAP) using regular programming language such as C/C++. SOAP Actor: This component fulfills SOAP requests. It is responsible for activating/creating objects, converting data, invoking methods, and packaging results. UDDI Interface: Based on SRL and our SOAP client library, the interface allows direct access to UDDI registries. SOAP Router: Based on WS_Routing protocol, the component adding and processing routing headers as either an intermediary or a final destination. The server is a bottom-up implementation of SOAP using C++ programming language. It works only on Windows platforms. History In late 1998, we started the development of an agent-based programming language. The basic idea is to create a set of tools to automate, to integrate and to aggregate existing web services; so that web services become reusable components for new generation of web applications. In March 1999, we implemented the first version of the Service Request Language based on XML, and created a couple of web agents that can collect information from the web. It is remarkably simple but powerful. The agents can utilize different protocols such as HTTP, HTTPS, FTP, SMTP and POP and collect/filter information as required. We could basically programming the web using these agents. In the mid of 1999, we created the dispatch center for controlling, synchronizing and collaborating agent operations. At this stage, we could dispatch hundreds of agents to collect information in certain categories from the Internet and integrate them into our own applications. In September 1999, SQLData began to actively involved in the development of MallAgent.com, a comparison shopping site that collects product information from hundreds of merchants in many product categories. We created a tool that can automatically generate web agents given a target web site. This greatly reduced the amount of work for programmers. In December 1999, we decided to have a full scale development of MallAgent.com and to bring it live in two months. On February 14, 2000, MallAgent.com went live. The site, unlike other web sites, is driven 100% by XML files. While others use XML as a tool of presentation and representation, we used it as a control language. More importantly, we proved that programmable web can be achieved using XML/SRL with no modification to existing HTTP services. In other words, the widely available HTTP services do not need to understand XML, SRL or SOAP in order to become programmable web services. In late August 2000, SQLData started the development of a version 1.0 SOAP server. The first version was developed based on SCL and quickly became obsolete. We then turned to SDL (Service Decryption Language ) and saw our effort became fruitless. On October 20, 2000. Our SOAP Actor components and SOAP Client library were tested. The components were then integrated into the SQLData Enterprise Server. The new server is named SQLData SOAP Server. The SOAP Server, unlike all other implementations, is capable of accessing both SOAP services and non-SOAP services. It is written completely in C++ and has no dependency on any other SOAP implementations. On December 11, 2000, we registered SoapClient.com and SoapAgent.com for hosting SOAP services and providing SOAP related technical information. The site went live two weeks later, powered by SQLData SOAP Server. On January 20, 2001, the Universal Description, Discovery, and Integration (UDDI) Service went live. It is SOAP Client service to live UDDI registries operated by Microsoft, Ariba and IBM. Users can search companies and drill down to service details through the SOAP interface. On February 10, 2001, Our SOAP Server was validated to be SOAP 1.1 compliant at UserLand. The server can virtually handle any data types, simple or complex, in SOAP request messages, although it's up to message handlers to support them. Another nice feature of the server is that it works well with or without Service Description Language. On February 17, 2001, SQLData released the SOAP Client Library version 3.0. It is an independent implementation of SOAP 1.1 with many powerful features. Message template, which is the key behind the UDDI browser service, is revealed partially in the user document. On March 24, 2001, We released a SOAP transport library that can deliver SOAP messages using many protocols such as SMTP, HTTPS, CMC, MSMQ and MAPI. May 23, 2001, our UDDI Browser can automatically bind to web services listed in UDDI registries and execute SOAP services online. It is the first such tools that can seamlessly integrate SOAP and UDDI services. June 8,2001, RSS Reader was released. It aggregates news feeds from different sources and allows user to read summaries online. July 17,2001, SOAP attachment was implemented. Interoperability is still an issue. October 4, 2001, WS_Routing protocol was added into our SOAP products. We successfully exchanged messages with Simon Fell's implementation and Robert Cunnings's implementation. December 2, 2001, XML Canonicalizer debuted. It is a tool for transforming XML documents into standard formats. The tool is part of the SQLData SOAP Security package. December 14,2001, Security features, XML Encryption and XML Signature , were added into the SOAP client and server. It took a little over three months to implement, but still left some rough edges in the first release.

About SoapClient.com

General Information

SoapClient.com is a resource center for SOAP developers. We provide product information, SOAP tools, and SOAP services such as web search and data access.

You can reach us at: info@sqldata.com.

Technical Information

The site is powered by SQLData SOAP server with the following key components:

SOAP/HTTP client: The client is compatible with almost all well-known SOAP implementations. It provides direct access to other web services using web browser.
WSDL/SDL/WSML Parser: The component parses and validates service description files of different kinds. It uses SAX 2.0 XML parser as basis.
SOAP Security: The component performs XML encryption and XML Signature operations, and secures sensitive data inside SOAP messages.
SOAP Transport: The component provides extensible wiring methods for SOAP messages. Currently supported transports include HTTP, HTTPS, SMTP, and MSMQ.
SRL Processor: This is the Service Request Language processor, which is the key part of SQLData Integration Server. SRL is a much higher protocol than SOAP. It allows direct access to all HTTP services (SOAP or non-SOAP) using regular programming language such as C/C++.
SOAP Actor: This component fulfills SOAP requests. It is responsible for activating/creating objects, converting data, invoking methods, and packaging results.
UDDI Interface: Based on SRL and our SOAP client library, the interface allows direct access to UDDI registries.
SOAP Router: Based on WS_Routing protocol, the component adding and processing routing headers as either an intermediary or a final destination.

The server is a bottom-up implementation of SOAP using C++ programming language. It works only on Windows platforms.

History

In late 1998, we started the development of an agent-based programming language. The basic idea is to create a set of tools to automate, to integrate and to aggregate existing web services; so that web services become reusable components for new generation of web applications.
In March 1999, we implemented the first version of the Service Request Language based on XML, and created a couple of web agents that can collect information from the web. It is remarkably simple but powerful. The agents can utilize different protocols such as HTTP, HTTPS, FTP, SMTP and POP and collect/filter information as required. We could basically programming the web using these agents.
In the mid of 1999, we created the dispatch center for controlling, synchronizing and collaborating agent operations. At this stage, we could dispatch hundreds of agents to collect information in certain categories from the Internet and integrate them into our own applications.
In September 1999, SQLData began to actively involved in the development of MallAgent.com, a comparison shopping site that collects product information from hundreds of merchants in many product categories. We created a tool that can automatically generate web agents given a target web site. This greatly reduced the amount of work for programmers.
In December 1999, we decided to have a full scale development of MallAgent.com and to bring it live in two months.
On February 14, 2000, MallAgent.com went live. The site, unlike other web sites, is driven 100% by XML files. While others use XML as a tool of presentation and representation, we used it as a control language. More importantly, we proved that programmable web can be achieved using XML/SRL with no modification to existing HTTP services. In other words, the widely available HTTP services do not need to understand XML, SRL or SOAP in order to become programmable web services.
In late August 2000, SQLData started the development of a version 1.0 SOAP server. The first version was developed based on SCL and quickly became obsolete. We then turned to SDL (Service Decryption Language ) and saw our effort became fruitless.
On October 20, 2000. Our SOAP Actor components and SOAP Client library were tested. The components were then integrated into the SQLData Enterprise Server. The new server is named SQLData SOAP Server. The SOAP Server, unlike all other implementations, is capable of accessing both SOAP services and non-SOAP services. It is written completely in C++ and has no dependency on any other SOAP implementations.
On December 11, 2000, we registered SoapClient.com and SoapAgent.com for hosting SOAP services and providing SOAP related technical information. The site went live two weeks later, powered by SQLData SOAP Server.
On January 20, 2001, the Universal Description, Discovery, and Integration (UDDI) Service went live. It is SOAP Client service to live UDDI registries operated by Microsoft, Ariba and IBM. Users can search companies and drill down to service details through the SOAP interface.
On February 10, 2001, Our SOAP Server was validated to be SOAP 1.1 compliant at UserLand. The server can virtually handle any data types, simple or complex, in SOAP request messages, although it's up to message handlers to support them. Another nice feature of the server is that it works well with or without Service Description Language.
On February 17, 2001, SQLData released the SOAP Client Library version 3.0. It is an independent implementation of SOAP 1.1 with many powerful features. Message template, which is the key behind the UDDI browser service, is revealed partially in the user document.
On March 24, 2001, We released a SOAP transport library that can deliver SOAP messages using many protocols such as SMTP, HTTPS, CMC, MSMQ and MAPI.
May 23, 2001, our UDDI Browser can automatically bind to web services listed in UDDI registries and execute SOAP services online. It is the first such tools that can seamlessly integrate SOAP and UDDI services.
June 8,2001, RSS Reader was released. It aggregates news feeds from different sources and allows user to read summaries online.
July 17,2001, SOAP attachment was implemented. Interoperability is still an issue.
October 4, 2001, WS_Routing protocol was added into our SOAP products. We successfully exchanged messages with Simon Fell's implementation and Robert Cunnings's implementation.
December 2, 2001, XML Canonicalizer debuted. It is a tool for transforming XML documents into standard formats. The tool is part of the SQLData SOAP Security package.
December 14,2001, Security features, XML Encryption and XML Signature , were added into the SOAP client and server. It took a little over three months to implement, but still left some rough edges in the first release.



Home \| SOAP Tools \| UDDI Browser \| Resources \| Source Code \| RFCs \| News Reader \| SOAP Interop \| Bookmarks