Forum Moderators: coopster
I made a script that iterates through the URLs and checks them with fopen();, flags and de-activates them accordingly. Currently there are 2K links, I would not expect to grow beyond 10K.
fopen(); seems to hang (even after breaking my while query into smaller batches). From what I understand fopen(); has the propensity to have trouble with paths that end as a directory without an explicit file name.
fopensock(); seems to be more robust, however I don't really needs all of it's features (detecting 302's etc.)
Any advice would be appreciated.
Scott Geiger
The O'Reilly PHP Cookbook seems to favor it over fopen(), fsockopen() and PEAR's HTTP_Request class,...they probably know what their talking about.
LOL. If you consider the library as a whole - yeah. But we're talking about a limited selection of functions that should provide a quick and relatively painless solution. I suppose you could also write something in C++ or JAVA and execute it server side if you had the wherewithall to develop and implement it. But why would you when you have a ready made set of functions available? ;)