On Thursday 03 May 2007 01:18, Martin Paljak wrote: > On 03.05.2007, at 1:36, Martin Preuss wrote: [...] > > - the master-slave model described in the document Micha linked to > > in his > > mail), this is needed for thin-client support provided for Gnumed > > Quickly going through the doc - the only reason for this is the > remote access reason, right ? [...]
Kind of... What I need in my particular case is to handle a scenario where there is a central daemon to which other hosts register their readers upon startup and unregister them upon shutdown (either explicitly or by disconnecting). This is a bit special to my situation but nevertheless I need it. [...] > > It *does* work over PC/SC, but that interface doesn't let me use > > CTAPI drivers > > so it excludes those readers for which there only are CTAPI drivers > > (which > > could of course be circumvented by adding an IFD-CTAPI wrapper). > > On windows - do you use CTAPI drivers and are there any readers that > only have ctapi and no pcsc drivers? [...] Not under Windows (as far as I know), but under Linux: Yes. [...] > Three issues I can harvest: > > 1. CTAPI bridge for pcsc (Possible to use code from openct?) > 2. remote connections (should work with all combinations and > hopefully be cross platform as well) > 3. memory cards (No real solution ?) [...] Libchipcard has that as well, and that's why I'm still developing and using it. I don't prefer OpenCT over PC/SC because I don't think it should be our job to write drivers (let alone special to one interface, e.g. OpenCT doesn't use IFD or CTAPI drivers but defines its own driver type) but rather to make them available to the application in a generic API. Regards Martin -- "Things are only impossible until they're not" AqBanking - http://www.aqbanking.de/ LibChipcard - http://www.libchipcard.de/ _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
