Jacob Hanson wrote:
> Hello everyone,
> I've nearly completed porting of Flash remoting to Python, "PyAMF", a
> la AMFPHP for PHP, FLAP for Perl, OpenAMF and FlashORB(?) for
> Java. For those
> that don't know, Flash remoting allows you to send structured
> data (objects,
> etc) from the server to the Flash client, using a compact
> binary protocol,
> without having to manually fuss with serialization and
> data-type conversions
> (big hassle). It generally accomplishes the same thing as
> SOAP (etc), but
> requiring a fraction of the bandwidth and using less CPU cycles on
> the client and server.
> I'd like to be able to support the implementation of it as a
> Webware plugin
> or module (and potentially other environments someday). I'm a
> newbie though
> (just installing now), so I'd appreciate any
> direction/pointers you can give me.
> What I need to do is to be able to load this thing up,
> currently implemented as a
> series of classes in single module. Then, most likely using
> servlets, being
> able to have complete control of the output, starting with custom HTTP
> headers followed by binary data.
I think there are some examples in the Wiki of sending PDFs which would be
an example of using custom headers and binary output.
> I'm all about performance, so ideally this module would be
> loaded once with the
> server and remain in memory for subsequent requests. This is
> the main appeal
> over using the PHP version, which has to be loaded for each
> request. Is there
> anything special I need to do to facilitate this or does
> Webware take care of
> this for me?
Webware only reloads servlets if they have changed on disk, and never
reloads other modules, so this is automatic.
> ...I'd also like to get this working with db-pool and
> userkit(is anyone
> working on userkit)?
You're on your own there... people do use dbpool, but very few seem to use
> Back to combing through the docs and wiki...
Another suggestion -- you may not need to write a full-fledged "plugin" but
instead just providing a servlet base class may be enough -- along the lines
of the XMLRPCServlet.