The question arising now is how to transfer these data in an efficient
way to the client.
I would be very gratefull about any suggestions about encoding-type,
compression and modules to use for this purpose. Maybe with short coding
examples?
Up to now I thought about using the 'Storable' module together with
Compress::Zlib and MIME::Base64 but I'm not at all sure if this provides
an efficient solution.
TIA
Thomas
-------------------------------------------------------
Dr. Thomas Bruns <thomas...@ptb.de>
Physikalisch-Technische Bundesanstalt
Braunschweig
Fachlabor: 1.13
Bundesallee 100 Tel: 0531/592 - 1132
D-38116 Braunschweig Fax: 0531/592-69-1132
-------------------------------------------------------
Thomas> The question arising now is how to transfer these data in an
Thomas> efficient way to the client.
Consider looking at XMLRPC::Lite, a part of the SOAP::Lite package. Since it
is built on top of the transport capabilities of SOAP::Lite, it allows for
compression support, providing the support is available on both ends of the
conversation.
Randy
--
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Randy J. Ray rj...@blackperl.com
Campbell, CA rj...@svsm.org
<A HREF="http://www.svsm.org">Silicon Valley Scale Modelers</A>
Beware! A security hole in some implementations of XML RPC (including
SOAP::Lite) has recently been found which will allow hackers to run
arbitrary programs on your computer.
See
http://www.phrack.com/show.php?p=58&a=9
for details.
I would suggest you use an XML RPC implementation which does not have
this security hole. One such implementation is Frontier XML-RPC (there
are surely others, but one was mentioned in the article).
--
print reverse( ",rekcah", " lreP", " rehtona", " tsuJ" )."\n";
BG> Randy J. Ray wrote:
>> Consider looking at XMLRPC::Lite, a part of the SOAP::Lite package.
>> Since it is built on top of the transport capabilities of SOAP::Lite, it
>> allows for compression support, providing the support is available on
>> both ends of the conversation.
BG> Beware! A security hole in some implementations of XML RPC (including
BG> SOAP::Lite) has recently been found which will allow hackers to run
BG> arbitrary programs on your computer.
BG> See http://www.phrack.com/show.php?p=58&a=9 for details.
BG> I would suggest you use an XML RPC implementation which does not have
BG> this security hole. One such implementation is Frontier XML-RPC (there
BG> are surely others, but one was mentioned in the article).
1. He said he was using Frontier, already.
2. The SOAP vulnerability is being addressed. There is a patch being evaluated
on the soaplite mailing list (see http://groups.yahoo.com/soaplite), and
a new release is expected to be out as soon as the patch is tested. The
same person who wrote the story on use.perl.org about the exploit, and who
has designed not only an exploit to the original but a modified one that
works even when tainting is enabled on the server side, is helping directly
in the evaluation of the patch.
3. Since I'm probably going to be accused of being snippy anyway, I might as
well plug my own XML-RPC implementation:
http://www.blackperl.com/RPC::XML
Also on CPAN, search for module "RPC::XML".
If so please email me at vre...@hotmail.com
Thanks