view release on metacpan or  search on metacpan

ChangeLog  view on Meta::CPAN

	All the internal use of object attributes in RPC::XML::Client
	now use accessors instead of the hash keys directly, to make it
	easier to sub-class the package. The same was done in
	RPC::XML::Server and to some degree in Apache::RPC::Server. The
	server classes are more likely to have problems, though.

	* lib/RPC/XML/Client.pm
	* lib/RPC/XML/Parser.pm
	* lib/RPC/XML/Server.pm
	The parsing of incoming data in the client and both server
	classes is now done to a streaming XML parser, eliminating the
	need for the full message to ever be in memory at once.
	Likewise, the client and server classes have new attributes and
	accessor methods to allow them to spool outgoing messages to
	files if the messages threaten to be too large to keep in
	memory (this is best used when dealing with a lot of Base64
	data that is being dealt with directly on disk as well).

0.46	Sunday December 29, 2002, 11:39:05 PM -0800

	* lib/RPC/XML/Client.pm

ChangeLog.xml  view on Meta::CPAN

      </description>
    </change>
    <change>
      <fileset>
        <file path="lib/RPC/XML/Client.pm" />
        <file path="lib/RPC/XML/Parser.pm" />
        <file path="lib/RPC/XML/Server.pm" />
      </fileset>
      <description>
        The parsing of incoming data in the client and both server classes is
        now done to a streaming XML parser, eliminating the need for the
        full message to ever be in memory at once. Likewise, the client and
        server classes have new attributes and accessor methods to allow
        them to spool outgoing messages to files if the messages threaten to
        be too large to keep in memory (this is best used when dealing with a
        lot of Base64 data that is being dealt with directly on disk as well).
      </description>
    </change>
  </release>
  <release version="0.46" date="2002-12-29T23:39:05-08:00">
    <change>