NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in eval.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Question to the author... (Score:2, Interesting)
I look forward to reading your book as I've only ever used LWP in the shallowest way, and found it hard to find any material to let me cross over to "full-blown" use, but I was wondering if you could answer an LWP question for me (cheeky I know, but you can always say no).
A few years back I wrote HttpSniffer.pl [schmerg.com] as an HTTP tunnel, or monitor (cf xmon) as I think of it - this was for debugging cookies and similar headers for scripted pages, but has proved quite popular for other people. At the time, LWP was all about being an HTTP client, but HttpSniffer has to play both client and server and should NOT follow redirects etc. so I wrote all my own HTTP handling code.
Now I understand LWP has been extended over time - so I was thinking about re-writing HttpSniffer using LWP - if it makes it easy for me to read and write the HTTP stream without modifiying it in any way... any hints, clues or gotchas that I should look out for, or do you think it should prove ridiculously easy.... ??
Cheers and TIA
T
Reply to This