SOAP is a protocol for communication about the importance of the Internet, because most of the fact that it has become natural for a great development platform. SOAP is a protocol has also been very stable. WS-* War of the early years of the new millennium seems to die, and some very useful extensions to SOAP has been selected by the market.
Soap Many tools are also stabilized by the protocol. Inadequate compared with other SOAP good game. Unlike other tools are still very easy to use for most applications. But as more people and more literal document as a method of broadcast encryption option, the roots of prejudice and SOAP RPC started to show, and the kit is not possible:: Lite with XML.
As a result of the SOAP:: Lite has some compatibility issues with more modern servers, and clients are known. Responsible for SOAP:: Lite is now difficult. Sources note the signs of a complicated, serious intelligent Kulchenko Paul creates the SOAP: Lite. Result, the harassment experienced Perl programmer, and that makes many of them are done in the fear of the court. I am the highest recognition given to my office to join the module to the fact that – I work with some bright programmers with experience in Perl and everyone looks the SOAP:: Lite. And not as an impression of “good” surprise that people are healthy, but fear.
But I’m not trying to inflate my ego, I tried the stage for what should only be established in addition to SOAP Perl kit.
If SOAP:: Lite as an exciting project, the authors will be processed, it is essential that SOAP:: Lite to manage your code base much easier. SOAP:: Lite can be written to benefit large sectors of the house a lot of code before the record is very mature, before the era of WS-I, when the toolkit and other servers have been agreed and adopted a set of best practices. It should also be given the option to XML: RPC protocol is completely different under an entirely different set of conditions. SOAP:: Lite should switch to a model based on documents, instead of being pushed into a People’s Republic of China.
Therefore, SOAP:: Lite-writing. SOAP:: Lite must live “Lite” in its name. SOAP:: Lite should be built from scratch to meet the WS-I. Initially be built around the bad WSDL parser and engine. There should be more modular, so components can be easier to implement new and improved, no change for users and developers. You should take advantage of some Perl modules that have developed SOAP:: Lite are designed to reduce code complexity and ambiguity.
SOAP:: Lite needs your help. SOAP:: Lite needs a group of 2-3 people want to see the cooling kit is essential for developers of Perl and welcome a new era of recycling, communities, small businesses, the use and usefulness.
Running a project like this is not a trivial task. Which took many months of time and attention. And then they should be encouraged and nurtured.
The project is not from the beginning. This is the vision and the various codes that have been tested in SOAP:: Lite does not need to waste disposal. What we do is try, SOAP:: Lite easier to handle and easier to grok. What we hope to create a new module, called SOAP: Simple.