Peter:
Hello! To your questions:
1. I've tested the echoServer with ~100 groups before, but never with
300, with one "admin" user assigned to all groups. The structure is
scalable, though, so I don't see why it wouldn't work. Any news when
you see it would be very helpful!
2. Yes, #2 is solvable with srvany. Alternatively, you could try the
"TightVNC with echoWare" server that we have, but it will not have
the same functionality as the UltraVNC server you're used to.
3. We're adding a capability to the 1.5 release of EchoVNC and the
echoServer so that a connection group can optionally have it's
membership "public". EchoVNC will then use the information to
build a more easily used GUI. I expect to see those versions
available by the end of the month.
cheers,
Scott
On May 31, 2006, at 12:36 PM, Peter White wrote:
> I wonder if you could please shed some light on these issues? We
> are considering running echoServer on Linux. We presently have
> over 300 customers and growing. Each customer has their own
> business with one or more locations. We do not want customers to
> get into each other’s sites but we do need our support people to
> get into all the customer sites. I have #2 handled with srvany.
>
>
>
> Thanks
>
> Peter White
>
> Integrated Dealer Systems
>
>
>
> My preliminary testing of EchoVNC has revealed the following
> potential issues:
>
>
>
> 1) Each customer will have to be set up as its own group for
> security purposes. The IDSADMIN user will then need to be added to
> each of these groups. We will want to test to make sure there are
> no issues with one user being a member of 300+ groups.
>
>
>
> 2) The UltraVNC Server can run as a service on the client machine
> but EchoVNC does not run automatically until startup, therefore we
> would not be able to connect to the server until someone has logged
> onto the machine after a reboot.
>
>
>
> 3) The dropdown list of VNC clients is a local list of clients
> that EchoVNC has tried to connect to previously. Ideally it would
> poll the Echo Server for currently available VNC clients. It will
> be necessary to know either the IP Address of the VNC Client or the
> client’s exact VNC username.
>
>
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
