Tim,
While I understand the need, I'm just a bit concerned with one item: GDC is more or less a browser ; it reads a UI description from the network (HTML / AUI Tree), builds the interface and reacts to end user actions.
Now: would you be happy if, when you connect to
4js.com, we would be able to know that you're connected at the same time on your bank web site, on amazon and on your favorite band's myspace home page ?
I presume no, and this is what I try to underline.
4js.com should only know that you're connected at the same time on the forum and the support page, but nothing else.
For me, your initial request is valid, but I would prefer we offer you something more server centric.
Having this on the server side as for me many advantages:
- works with any front-end (don't care if half of your processes are used for GWC, half for GDC)
- there is no privacy concern
- it shows really the use of your server. If this is done on GDC side, you will know what is running on a specific GDC. If you've 100 different users (or 1 user running 100 GDC using -n option), you'll see that each GDC runs 1 application and this will look ok, while 1 user running 50 applications would be considered as an issue.
I know that GDC can already do lots of things against privacy, but this was done in early days mainly for compatibility reasons (good old rcp deamon from Wtk) and today's trend is to provide more and more safe guards in this area.