Re^4: A case where Mechanize works, LWP doesn't

Great questions. The reason is two fold.

1. Limit change. The existing PERL installation doesn't use Mechanize and I would rather not introduce it primarily to keep the politics under control.

2. POE integration. I have seen much on LWP and POE but nothing on Mechanize and POE. I'd rather go with a more proven route.

Correct me if I am wrong (with a URL, ISDN or other tangible reference) especially on #2

Comment on Re^4: A case where Mechanize works, LWP doesn't

Replies are listed 'Best First'.
Re^5: A case where Mechanize works, LWP doesn't by Corion (Patriarch) on Feb 10, 2010 at 20:11 UTC
As WWW::Mechanize ISA LWP::UserAgent, most of the techniques used to make LWP::UserAgent cooperate with POE will work with WWW::Mechanize as well.	[reply]
Re^6: A case where Mechanize works, LWP doesn't by dneedles (Sexton) on Feb 10, 2010 at 20:36 UTC
Ok. I wanted the luxury of being a bit lazy with a couple pre-chewed POE & Mechanize examples, but alas I want my autistic son to sleep more than an hour at a time and that ain't going to happen either. 8-) Thanks for the help. I am leaning toward the political fight as it seems Mechanize will lend to more rapid development and a more robust solution than via straight LWP.	[reply]
Re^5: A case where Mechanize works, LWP doesn't by ambrus (Abbot) on Feb 12, 2010 at 20:31 UTC
As a last resort, you could try LWP::Coro with POE (I'm not saying it works), or fork a separate process to do the downloading. Try that only if you really can't solve the original problem of doing the query without Mechanize, and if you really can't get rid of POE.	[reply]