At 05:14 PM 2/24/2001 -0800, Paul Kulchenko wrote:
>That's right, but first Perl caches calls that involve inheritance
>and second, I use the same scheme, because arrays can have everything
>inside and I need to call serialization function for every element in
>array. I did profiling for several versions and did some
>improvements, but there is no obvious stopper.
Is there any way to add an interface to basically provide serialization and
deserialization hints? My experience in the way we use SOAP is that there
are only a few core objects that really require SOAP and the rest can be on
the front-end.
Maybe using a CORBA-like IDL config? Thus, I could give a strong hint to
SOAP::Lite that a particular array only contained one type of object...
In the stuff I've been doing over the last year, I've always wrote my own
serializer/deserializer from scratch because I wanted it to be fast and
have control over optimization rather than using the libraries that already
exist out there.
Later,
Gunther
