Pickled objects over the network

Walker Lindley brotherjenos at gmail.com
Fri Jul 20 17:27:13 CEST 2007

It doesn't interface well because the string you end up with often doesn't
fit into a single packet. Therefore you have to add a layer of protocol on
top of it that allows you to check to make sure you have the whole string
received before trying to unpickle it. This the case even if you use
socket's makefile() method to make a file descriptor.


On 20 Jul 2007 14:00:06 +0100 (BST), Sion Arrowsmith <
siona at chiark.greenend.org.uk> wrote:
> >Since pickle has problems
> >-- does not interface well with networking
> In what way does pickle not interface well with networking? Other
> than, possibly, security issues which you list as a separate problem
> with it. I've taken a working XML-RPC system and replaced the XML with
> pickle, and had no issues. Other than an order of magnitude
> performance gain. (OK, a cow-orker allegedly and unreproducibly found
> that cPickle was leaking memory, and as the performance gains weren't
> so great with the pure Python implementation, it got shelved and we
> stuck with XML-RPC.)
> --
> \S -- siona at chiark.greenend.org.uk -- http://www.chaos.org.uk/~sion/
>    "Frankly I have no feelings towards penguins one way or the other"
>         -- Arthur C. Clarke
>    her nu becomeþ se bera eadward ofdun hlæddre heafdes bæce bump bump
> bump
> --
> http://mail.python.org/mailman/listinfo/python-list

This e-mail is licensed under the Creative Commons
Attribution-NoDerivs 2.5License. To view a copy of this license, visit
http://creativecommons.org/licenses/by-nd/2.5/ or send a letter to Creative
Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20070720/3cabbc0d/attachment.html>

More information about the Python-list mailing list