SPUG: Generic Client/Server building blocks

[Brian Hatch]

I'm going to be writing two client/server apps in the
next few weeks that are pretty dead simple - log in,
send some parameters, get some data back, rince lather
repeat.  Totally different data and requirements.
One will probably require authentication, other won't.
One may provide different data depending on user
authenticating.

My first thoughts were to write some TCP protocol that's
SMTP-ish.  'helo / starttls / auth / get blah / etc'.
But then I thought that's just silly, and would be annoying
to those folks who need to write clients in non-perl code
because then I can't just hand them my module.

So I was thinking SOAP, because it's all the rage.  Got
me thinking "Soap::Transport::TCP or Soap::Transport::HTTP
would let me build the server", but didn't see an instant
way to have it use SSL in the server.  (Client code can
do SSL just fine.)

Anyone tried doing this sort of thing?  Pros/cons?  Or
should I just write YACP[1] ?


[1] Yet another custom protocol.
needs 'https' instead


-- 
Brian Hatch                  "Dirt is used to everyone walking on
   Systems and                it. Just like Zathras, but we've come
   Security Engineer          to like it. It is our role. It is our
http://www.ifokr.org/bri/     *destiny* in the universe."

Every message PGP signed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://mail.pm.org/pipermail/spug-list/attachments/20050523/53a520b5/attachment.bin