Brown trousers time :~

Lyle - perl at
Wed Oct 10 19:44:40 BST 2007

Paul Orrock wrote:
> I think what I was trying to get at was that the best way to do this 
> would be to have the click tracking engine (that actually gets told by 
> the browser "i have visted page x") completely outside the webserver 
> serving the site.
> Client site can be served by any webserver / technology I 
> want to. To use your tracking engine all I have to do is put a piece 
> of html in my pages that requests an image of 
> is a simple http server which I'd probably base on 
> something like Net::Server::PreFork and put in the bits of HTTP that I 
> need to get the cookie, the referrer and the client id. It then stores 
> these in the database or flat file and returns a 1px x 1px gif which 
> can be set to not even display on most browsers by setting width and 
> height to 0.
> There are a load of advantages to doing this, it's easily extensible, 
> about as fast as you could make it without much effort, it's easily 
> configurable and also you could compile it into an executeable to run 
> on any platform, oh and the whole thing is written in perl. :-)
Certainly sounds interesting... I'll be tracking clicks as well as hits, 
but I guess it would work in a similar way as well. Are you talking 
about perlcc to make it executable?


More information about the mailing list