Re^2: http::daemon::threaded

Im trying to install as little as possible. This 'package' will go on 3-500 client machines. The less I need to install and maintain the easier my job will be.

Im hoping that by creating a standalone SOAP daemon that I can then focus on the classes that run 'behind' it instead of worrying about keeping up the infrastructure around it.

I will be the only person communicating with this daemon (through a series of perl scripts hosted on local servers) so it doesn't need to be able to juggle dozens of simultaneous clients nor does it need to be super-flexible w/re its configuration.

It does need to be as secure as I can make it as I will be transporting HIPAA protected information through it.

Comment on Re^2: http::daemon::threaded - soap?

Replies are listed 'Best First'.
Re^3: http::daemon::threaded - soap? by kingkongrevenge (Scribe) on Aug 04, 2007 at 13:58 UTC
Don't know anything about threaded, but you could just make a plain old forking server based on HTTP::Daemon. You can then restrict access by checking the peer address, as H:D is an instance of IO::Socket::INET. You could create a session id (url?id=12345) and append it to URLs. Reject requests without the ID. You can generate cookies from one of the CGI packages. Just stick them in the HTTP::Response and send it. Pull them out of the headers.	[reply]

Replies are listed 'Best First'.

Re^3: http::daemon::threaded - soap?
by kingkongrevenge (Scribe) on Aug 04, 2007 at 13:58 UTC

You could create a session id (url?id=12345) and append it to URLs. Reject requests without the ID.

You can generate cookies from one of the CGI packages. Just stick them in the HTTP::Response and send it. Pull them out of the headers.

[reply]