in reply to /^mod_perl/ && Persistent DBI

Do not invent protocols. Use SOAP::Lite to set up a mini-SOAP HTTP server on the first hit, then subsequent hits will reuse that server. Have it time out after some number of minutes, and you automatically get lightest weight persistence.

You can use HTTPS to talk to the mini-server, and certificates to ensure client authenticity. That should handle your eavesdropping/authentication issues.

-- Randal L. Schwartz, Perl hacker

Replies are listed 'Best First'.
Re^2: /^mod_perl/ && Persistent DBI
by Aristotle (Chancellor) on May 29, 2002 at 19:18 UTC
    Can you be more verbose? The module documentation seems to be just as terse as your description. A slightly more detailed description of the kind of framework that would be required would be nice - my main question is how one would set up that SOAP server. fork()? Unlikely, and certainly for a proposition coming from you. *grin*

    Makeshifts last the longest.

[reply]
[d/l]
      Google searching Soap::Lite returns the Soap::Lite homepage, which explains the protocol & design patterns...


      ----
      Zak - the office
[reply]

In Section Seekers of Perl Wisdom