Hi, As Philip Perry said, it is impossible to do this just as it is.
Your problem is obvious if you know the XServer protocol. The aim of XServer protocol is that the application runs on the Server and only the display is on the Client. The Terminal Client received only the windows display by a local X Display Manager. The windows are generated by the program running on the ressources of the Server and forwarding by the an XServer running here to the Client. The application don't know if this windows are forwarded and it is not its problem and consequently this program has only access to Server's ressources. Thus only the readers connected on the Server are available for the application. But I think there is a simple solution for your problem. On all your clients, install PC/SC and connect a reader. When it works, write for the clients a simple program (that we can see as a layer over PC/SC) opening a TCP/IP socket and mapping the commands received on this socket in commands for local PC/SC daemon. This program will dialog with PC/SC daemon and will forward the responses on the socket. On the other hand of the socket you may have the Server. A problem with this solution is that your application must know the client who displays it. It is the application that dialogs directly with the TCP/IP server of the client. An other solution is to let your application speaking with an other PC/SC daemon running on the Server and to make an dummy ifdhanler for it. This handler must be able to connect to the TCP/IP server of the client. Perhaps this idea is conceptually more beautiful. The problem is always that the PC/SC daemon must know its clients. I think there is a solution in this way but it is not my job ! ;-) For your Java applet you can use OCF and OCF to PC/SC bridge or the JPCSC. Good luck, Damien Sauveron Selon Aswartha Narayana <[EMAIL PROTECTED]>: > Dear All, > I have a requirement where there will be terminals (thin clients) that > will be connected to a terminal server. The terminals connect to the > terminal server using XServer. All the processes that need to be > executed on the terminal gets executed on the terminal server it self. > > One of the application , a java applet that is embedded in a webpage > should talk to the smartcard reader connected to the terminal. When i > try to connect the reader thru my applet the application is searching > for a smartcard on the server and not on the terminal. > > We are using the pcsc-lite 1.0.1 that is downloaded from this site. We > want to modify our application such that it establishes a connection > with the terminal's pc/sc manager and not the server's. > > My basic doubt is " > Can this be possible with pcsc-lite 1.0.1? Or should i download the > new 1.1.1 rpm (Redhat) and install? > Is it a must that the pcsc daemons run on both terminal aswell as > server? > > We tried with two standalone systems with Redhat 8.0 with one system > having the smartcard reader connected and pc/sc daemon running. No card > reader is connected and no pc/sc daemon is runnig on the other system > I used the "formaticc.c" from your site for testing. > > One the system with smartcard reader and daemon connected and with > hostname it returned the reader name connected to that pc. Even when i > changed the host name to some other IP (of the second system) the > application returned the same reader name that is connected to the first > PC. > > When i ran the same application on the second pc without reader and pcsc > resource manager there was an error message saying that context could > not be established. > > Please let me know what i should do to over come the problem > > Appreciating your quick response at your earliest convenience. > > Thanks and regards > Aswarth > > > > > _______________________________________________ > Muscle mailing list > [EMAIL PROTECTED] > http://lists.musclecard.com/mailman/listinfo/muscle > ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
