On Thu, 19 Oct 2006, Michael Bender wrote:
I'd like to add SCARD_E_INVALID_DISPLAY to the list of err consts
in PCSC/pcsclite.h [...]
Are the list of error/status return codes controlled by the PC/SC
specification itself, so that we are not really at liberty to add
or change codes as we like, or is there not such a tight binding
between what PC/SC-lite and the PC/SC specification for the client
side API (via libpcsclite.so) provides?
I'm thinking of this specific case where we introduce a new error
code, but no applications know about it, so no one uses it, so that
in effect it doesn't provide any additional value?
Hmmm... and how would you determine if the display is invalid?
consider the problem of some visualization systems... Muliple graphic
displays are/can be installed in one system.
Two (or more) heads, each with a separate X server...
The best bet I can think of currently is to create a new Input module
for the X server. It would be controled/managed by the X server, but not
used for input or output OTHER THAN to direct/redirect/control the data
stream to/from the card reader and the pcsd server.
For security purposes, it is normally a VERY good idea to abort the X
server and restart it for the next user. This should allow the X login
application to slave all input (including the card reader) just as
it slaves the keyboard and mouse.
This would also eliminate the problem of display control (which reader
goes with which graphic head) by allowing the hardware + X server to
determine the matching devices, just like it does for keyboard/mouse.
It would also eliminate the problem of a user attaching to the device
without using the X server.
Just a thought.
mike
--
[EMAIL PROTECTED] Sun Ray Product Engineering
I don't speak for my employer. My opinions are not necessarily those of
Sun Microsystems, Inc. or any of its wholly-owned subsidiaries.
_______________________________________________
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: [EMAIL PROTECTED]
Any opinions expressed are solely my own.
_______________________________________________
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle
