Pavel,
you beat me to a punch! But this is what so great about having people who really know their stuff!
Here are my thoughts on the project. Needless to say, I would like to hear what everyone else is thinking about it, and then base our development on the mutual consensus. I hope that someone is better organized than me and is able to put it together in a nicer way so we can post it for everyone to comprehend without reading through all of my jibberish blabbering.
My initial preference was to suggest C#, but considering that many people are iffy about using .NET or installing it on their machines, I suggest starting with VB for the prototype and then as it gets more stable move to C# (which is not that much different). There are a lot of langauages out there, Java is probably another contender, but I would suggest VB if people do not mind, because it means more people can contribute to the initial design and help us with the coding (plus I am not that good in it too)
Regarding how to collect statistcs, StatServer SDK would require additional licenses and many of our clients do not want to pay additional license fees. Genesys ActiveX is probably the most commonly used component so everyone would have no problem with it. JTAPI is another alternative, but ... well, it IS JTAPI, guys
OS - let's keep it Windows for debugging sake
We will need some fundamentals to start the discussion on, so, I will try to put together a draft over the next few days, and then start from there.
The initial layout would be :
Wallboard Server - collect Queue statistics, transmit information to client. Genesys ActiveX-based
Client - ActiveX based client which can be used As-Is or embedded into Browser. Displays Queue Name and relevant information
I suggest use of TCP and not UDP to avoid possible network-related chagrins and incurring wrath of the local network administrator. (Most of our clients do not allow for UDP between different segements)
(Ok, please feel free to add !!!)
Off to putting together our basic doc!
Vic