It all depends on the programming language. If you're using my method of choice, php and curl, then curl supports socks proxies straight out of the box at the http level with no need to go down to the socket layer.
It sounds like php is pretty damn nice, what are the drawbacks to it? It seems like i can save myself alot of trouble, but there's no GUI to it, right?
If your platform of choice is Windows then I don't think php is a good solution, it works but not nearly as cleanly as on *nix. If you're familiar with Windows languages then I'd just stick with that, it really doesn't matter what you write your stuff in as long as it works. I just use php because that's what I know. I'm sure that there must be a socks library for C# etc that you could just plug in to your script.
No there isn't any kind of built in GUI for php but IMHO that's an advantage. If you want to go industrial strength cranking out spam 24/7 on cron jobs, then running your scripts from the command line (on *nix) is the way to go. Some people write an apache interface to their php scripts so they can administer them through their browser rather than typing stuff in on the command line.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.