Hi, I need your opinions about questions for new design of clients handling. I have many questions for you and I give you my opinion.
1) Do you think that a mono-threaded application is allow to create more than one CONTEXT to a identical PC/SC Daemon by SCardEstablishContext in one thread? IMHO (In My Humble Opinion): I don't see the need. 2) Do you think that for multi-threaded application each thread must create a CONTEXT to the identical PC/SC Daemon if it wants to used it? Or do you think that a global context for all the thread is sufficient? IMHO: I think that for each thread a CONTEXT is needed. 3) If you think as me to the previous question. Do you think that each thread have only the right to close its context and not the contexts of her sisters thread? IHMO: yes and thus only to SCardDisconnect to the CHANNEL create in this CONTEXT (by SCardConnect). 4) Actually we have a serialisation of the requests in the scope of all clients. I think that we need a serialisation on the calls only in the scope of each thread of an application. PROBLEM: Actually for one application with 2 threads if you have put the --enable-threadsafe in the . /configure only one thread is executed and the other is stopped until the return of the first. GOAL: The goal of this new design is to have a more efficient PC/SC Resource manager in order to allow that a maximum readers dialog with a maximum card in the same time. I wait your feedback. Perhaps there are some problems that I have not see, or some goals that interest you or perhaps you have some ideas. Regards, Damien Sauveron ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
