distributed SQUID proxy and load balance "bandwidth partners" network system
Build/test/implement of a client/server system. Client sides involves config and wrap of 3rd party app (squid 2.7 for windows) in a custom "controller app"
wrapper. Server side includes several monitoring and controlling and admin functions. Server environment will be Linux based host, client environment will be
Windows XP Professional or Windows Vista. Client PC network environment will be broadband internet connection with dynamic IP allocation from ISP.
The general idea is to enable advertisers who wish to post more and faster to classified ad sites and web page advertisement locations (legal only) to use a
distributed network of "bandwidth partners" who donate their availabe CPU cycles and broadband bandwidth to the network in exchange for a share of the
resulting revenue pool generated by the content partner advertiser(s). The exact destination sites and login/user credentials and content that will be used
is completely determined by the content partner(s). the bandwidth partner(s) simply provide bandwidth and CPU, acting in practical terms as a distributed
proxy network by running a distributed client app and controller "wrapper" in their system tray, but limiting outgoing traffic to port 80 so there is no
potential for abusive activity by the content providers (since traffic content will be unregulated - so i.e. content providers could not just bounce traffic
in and then out to the internet to do potentially bad things on non-port 80). The content partners will set their own delivery/posting scripts/apps pointing
to the bandwidth partner network subdomain (as defined by the dynamic DSN service portion of this project) where the traffic will be distributed to load-
balanced bandwidth partners evenly listening via their SQUID app at <real IP:port> and then forward out via routine port 80 to the final web destination.
The project will require: 2 distributable client applications (for bandwidth partners: 1) a custom squid 2.7 for Windows and 2)a windows "controller" app wrapper ) and server applications/web pages with appropriate control panels for 1) system admin 2) "content partner" customers 3) "bandwidth partners"
see attached file for more complete description and PMB for specific questions. DOnt bid if you dont understand or cant do it.