#33 Refactor SOAP Lite into several modules

[Martin Kutter]

SOAP/Lite.pm has the unfortunate notion of agglomerating all packages needed in one file.

This is undesirable in many aspects:

* it reduces maintainability
Instead of just opening the file for a package, a developer has to search through SOAP::Lite to find the part of the source code in question

* it increases the memory footprint
By loading everything (including unneeded stuff, like a SOAP Server in clients), the memory footprint is increased without need.

* it increases complexity
Big modules with several packages are generally more complex than a bunch of small ones. The packages in SOAP::Lite can become interdependent in various aspects (circle usage, use of common globals) by accident.
Such interdependencies may cause subtle errors that are hard to spot and even harder to remove.

The suggested relief is to refactor SOAP::Lite into several packages.

In a first run the interface should remain unchanged, which means that the modules factored out are used in SOAP::Lite.

[Anonymous]

Logged In: YES
user_id=2014518
Originator: NO

Re-opened as need to add new files to META.yml