Re: message used serializer that is not accepted: 4

On 1-2-2014 17:28, Richard van Bemmelen wrote:
> It looks if its working now...
> 
> Apparently the /name server/ also needs to know the added protocol, not only the client
> and the server??
> I had exported the environment variables in another bash shell then were I started the
> name server from.

Yeah: when you are telling your client (or server) code to use a different serializer,
they will use that serializer too when talking to the name server.

This is not a problem unless you start using the pickle protocol which is disabled by
default, and so the name server will complain about it. You have to enable it in the
name server too.

At this time, there is no simple way to use a different serializer for different proxies.



Irmen


------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable 
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk