2004-06-25, 16:51
i have a basic comm function i've written that pickles an object into a string, sends the length of the string over a socket (so the receiving socket knows how long to listen), and then sends the object string.
then the receiving function unpickles the string back into a python object.
this is incredibly convenient for server/client relationships over a network, where you can actually pass a python object from the server to the client (in this instance, an opened image object).
my problem is, when i try to send anything to my xbox using this comm function, i get an error from pickle saying the string isn't reliable.
i can get the exact error message over lunch. just checking to see if pickle is supposed to work in xbmc.
then the receiving function unpickles the string back into a python object.
this is incredibly convenient for server/client relationships over a network, where you can actually pass a python object from the server to the client (in this instance, an opened image object).
my problem is, when i try to send anything to my xbox using this comm function, i get an error from pickle saying the string isn't reliable.
i can get the exact error message over lunch. just checking to see if pickle is supposed to work in xbmc.