Hi Uri, > https is just http over an ssl socket with a different port than > http. you can use IO::Socket::SSL for that. but the problems you will > run into are wide and varied which is why LWP is so large. if you know > your http transactions will be very basic and not need help, it is easy > to write a simple module. but it is so easy to get things wrong and when > it gets more complicated, you will want LWP.
The requests are going to be in the form of POST requests using structured URLs with an optional POST body payload, the responses will be JSON. I feel like that's simple enough to warrant a barebones module. That being said, I should probably write a simple socket module and do some tests to compare it to LWP to confirm that LWP has as much overhead as I think it does. Peter _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
