Re: [Wpg-proxy-development] What should a web interface contain?

[John S. <jo...@we...>]

SVN updated, we have a basic web page returned with usage statistics
presented via a web page when you point your browser at the proxy.
I added several methods to enable/disable this capability, and still need to
write a log4j appender that will collect 50/100/500 messages in a stack for
us to display in this page, but I will wait until we iron out the details of
what this page should do, and how it should do it, please respond whenever
you can to the questions in the original email, I hope this capability isn't
just an annoying window dressing that no one really wants. ;)
Thanks, John
 

-----Original Message-----
From: John Southerland [mailto:jo...@we...] 
Sent: Wednesday, January 31, 2007 11:13 AM
To: 'wpg...@li...'
Subject: What should a web interface contain?

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