Team,
I have been thinking about expanding a feature of the proxy server itself.
I want to make sure the proxy remains a simple library but I realize we also
need some level of instrumentation to allow us to debug and give developers
a simple way to troubleshoot their code. I had always intended to add a
simple web interface that will allow people to point their browser directly
at the proxy and get usage statistics.
This is a little tricky, but if we get a request that is not destined for a
remote host, but the proxy itself, then we can ignore the rules and return
some statistics such as:
Number of processors and handlers registered
Connection statistics such as number of requests processed and the
success/failure counts as well as durations
A simple log display of the last 50/100/500 messages logged
What other information would you like to see in a status page?
Should we user/pass protect this information?
Possibly allow enabling or disabling this feature via enableStatusBrowser(
Boolean ) and isStatusBrowserEnabled() methods?
Does this even seem useful? Or does it seem more "window dressing"?
I know I personally don't worry about such trivial things while developing,
but I wrote the stupid library, and know somewhat what is happening via
log4j.
I don't want to stop the progress going on, but think I can work this into
the code without breaking anyone elses changes.
Thanks, John
|
