WDDX vs native serialize.

[proman]

Hello,

I 'm looking for a way to comunicate servers, protocols for these purposes are
well known, but i want to make one 😉

WDDX is a good way for instance, it serialize to XML and deserialize to php value. But what are the advantages?

For example, with serialize($object) i can
serialize this instance of a class and transfer it without problem. The curious thing is that the class definition works as the same as that a DTD do....

... better than that, OO can replace XML? or why to use XML?

Thks++;

[Anon]

Hey Pablo,

There are a number of reason's to use WDDX
as your 'communication protocol'.
I'm only going to point our a couple
that I find handy at work.

First WDDX retains the data type.
Eg. Date remains a date and number remains a number.
Secondly, the big one, WDDX is usable in
loads and loads and loads of different languages.

We use PHP and ColdFusion as a web front
end for about 8 other servers ( ftp, mail, dns etc )
When the web server needs to tell something to
the mail or ftp or dns servers we use SOAP.
SOAP is an XML protocol.
The 'payload' of this soap call is an WDDX
packet.

This means the Linux box can have system scripts written in Perl,php, python etc, etc
as they all can deserialize the WDDX packet.

So WDDX is like the common language for
out array of Linux servers.

Hope my rambling makes sense :-)
Cheers
Rudi.