Daniel Dittmar wrote:
> > My client-server is Python-to-Python. At present, I am using cPickle to
> > transfer objects between the two. Among other things, I sometimes
> > transfer a tuple. Using JSON it appears on the other side as a list. As
> > I sometimes use the tuple as a dictionary key, thi
> My client-server is Python-to-Python. At present, I am using cPickle to
> transfer objects between the two. Among other things, I sometimes
> transfer a tuple. Using JSON it appears on the other side as a list. As
> I sometimes use the tuple as a dictionary key, this fails, as you
> obviously can
Alan Kennedy wrote:
> [Frank Millman]
> > I am writing a multi-user accounting/business application, which uses
> > sockets to communicate between server and client. The server contains
> > all the business logic. It has no direct knowledge of the client. I
> > have devised a simple message format
Frank Millman wrote:
> Hi all
>
> I am writing a multi-user accounting/business application, which uses
> sockets to communicate between server and client. The server contains
> all the business logic. It has no direct knowledge of the client. I
> have devised a simple message format to exchange i
> Yes, evaling JSON, or any other text coming from the web, is definitely
> a bad idea.
>
> But there's no need for eval: there are safe JSON codecs for python,
Fair enough. And I should imagine that the codecs are still much faster
and easier to use than XML for the same purpose.
For my purpose
[Ant]
>> I'd favour JSON if the data structures are simple personally. XML is
>> comparatively speaking a pain to deal with, where with JSON you can
>> simply eval() the data and you have a Python dictionary at your
>> disposal.
[Steve]
> Modulo any security problems that alert and malicious users
Ant wrote:
>>to use? I could go back to XML, or I could switch to JSON - I have read
>
>
> I'd favour JSON if the data structures are simple personally. XML is
> comparatively speaking a pain to deal with, where with JSON you can
> simply eval() the data and you have a Python dictionary at your
>
[Frank Millman]
> I am writing a multi-user accounting/business application, which uses
> sockets to communicate between server and client. The server contains
> all the business logic. It has no direct knowledge of the client. I
> have devised a simple message format to exchange information betwee
> to use? I could go back to XML, or I could switch to JSON - I have read
I'd favour JSON if the data structures are simple personally. XML is
comparatively speaking a pain to deal with, where with JSON you can
simply eval() the data and you have a Python dictionary at your
disposal.
I recently u
On 2006-06-08, Frank Millman <[EMAIL PROTECTED]> wrote:
> I would rather make a decision now, otherwise I will have a lot of
> changes to make later on. Does anyone have any recommendations?
Did you consider XMPP?
With XMPP you create XML streams between your server and the client.
XMPP is an open
Hi all
I am writing a multi-user accounting/business application, which uses
sockets to communicate between server and client. The server contains
all the business logic. It has no direct knowledge of the client. I
have devised a simple message format to exchange information between
the two.
At f
11 matches
Mail list logo
