On Saturday 01 July 2006 03:02, [EMAIL PROTECTED] wrote: > > Thank you very much. Unfortunately, the call center article was about > > kphones, not Skype. > > > > I briefly tried esddsp with Skype, and it didn't work. I'll keep trying > > it, > > though, with Skype and with other programs. I really appreciate the tip. > > > > Would it help if I put a sound card in the server? > > esd doesn't support full duplex audio, which you'll definately need, if > you want to run a voip client on the server, and have your headset plugged > into the client. In fact, even if it did support that, i've been told by > some people who are very knowledgeable in the audio world that trying to > run a voip client on a server, and display it on a thin client is a bad > idea. The latency would be noticeable. > > I think the proper way to run a voip client in a thin client environment > is to run the program ON the thin client. > > And, as for your question about having a sound card in the server, it > wouldn't help at all.
Jim, I don't believe the advice you've been given: I run skype on a thick client without any noticeable difference from the server. What we need to have to escape this mess (and I can't doit, but I'm trying): A driver on the server that connects /dev/dspN /dev/mixerN to a thin client /dev/dsp /dev/mixer (the network comms is fairly easy). Then skype (or other audio application of choice) displaying on clientMM, running on the server using /dev/dspN will talk to the hardware on clientMM totally transparently. The current mess of audio solutions, sortof solve generic problems. Local media support (kewl), now we need local audio support. details: The server-machine runs a network daemon The client-machine contacts the server-machine and connects soundcard, via network, to server-machine. The application, displaying on client-machine, running on server-machine uses server-machine /dev/dspN to talk to client-machine /dev/dsp Problems are: Managing the N part of /dev/dspN (what N does your skype use eg /dev/dsp37) The network-server-driver implementation. How it scales eg 10 clients? 255 clients? Maybe ... A paradigsm shift to thick-clients. Like LTSP, but everything happens on the clients, /home is /home on server. All processes run locally. A shared root NFS file system. (some of my clients have their own R/W file system, some LTSP) James Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
