Re: MUSCLE Opinions

1998-09-22 Thread franzini
On Mon, Sep 21, 1998 at 10:16:49AM -0500, David Corcoran wrote: > Ok, I need some opinions here. Basically I have run into a small problem with > the resource manager. Ok, BIG problem. When I load multiple ctapi libraries > into memory ( such as two Reflex 60's on different ports ), it only ref

MUSCLE and musclecard-1.6

1998-08-23 Thread Walter Franzini
My knowledge of smart card is little and is little my knowledge of musclecard. :) I have just got a look at musclecard's source and now I have some question for you: 1) How can musclecard support two or more reader ? I have seen only one handle. 2) How can musclecard handle a different interfa

Re: MUSCLE Important - Resource Manager API

1998-09-04 Thread Walter Franzini
On Tue, Sep 01, 1998 at 05:40:56PM -0500, David Timothy Corcoran wrote: > Hello, > > OK, I promised a look ahead at the upcoming resource manager for talking > to a variety of smartcard readers. Below is a visual representation of > how it all will fit together and the C resource manager API. P

Re: MUSCLE Update

1998-09-20 Thread Walter Franzini
On Sun, Sep 20, 1998 at 09:38:30AM -0500, David Corcoran wrote: > Hello, > > Here is an update on what is going on. You are doing a very good job. > 1 Finds reader in config file returns library and dynamically loads it. Where this files are located ? /usr/share/ctapi/ for config files /usr/lib

Re: MUSCLE naming convention

1998-09-26 Thread Walter Franzini
On Tue, Sep 22, 1998 at 05:46:49PM +0200, gregor wrote: > a ct-api should named like this: > > ctapi-n.xyy.so > > where n is a "well know identifier" > x the major-no of the release > y the minor-no of the release I suggest to use a different naming convention: libctapi-n.so.xyy whit the

MUSCLE CTAPI test program

1998-09-27 Thread Walter Franzini
Have someone already writed a program to test a ctapi library? I mean a `complete' test. With : 1) CTAPI implementation 2) CTBCS check 3) ISO7816-4 commands -- Ciao Walter. C makes it easy for you to shoot yourself in the foot. C++ makes that harder, but when you do, it blows away your whole

Re: MUSCLE naming convention

1998-09-27 Thread Walter Franzini
On Sun, Sep 27, 1998 at 09:22:03AM +0200, gregor wrote: > > OK, you're right. > > but then i would prefer > > libctapi-.x.yy.so > > because, there is no need for symoblic links Yes, but when you replace a library whit a newer version you must recompile all programs that depend on it. Usin

Re: MUSCLE naming convention

1998-09-27 Thread Walter Franzini
rn Sun, Sep 27, 1998 at 01:09:53PM +0200, gregor wrote: > ok > so the lib should look like: libctapi-n.so.x.yy > and the link: libctapi-n.so > > is that correct? > Yes. Remember also the link libctapi-n.so.x -- Ciao Walter. C makes it easy for you to shoot yourself in the foot.

Re: MUSCLE CTAPI test program

1998-09-27 Thread Walter Franzini
On Sun, Sep 27, 1998 at 09:33:55AM -0500, David Corcoran wrote: > No, not yet. Are you up for it ? It would be really nice to have > something that tells what is wrong with a person's CT-API library. Yes. I hope to finish CT-API for the Argus 210 CT in a couple of weeks, but I want test my w

Re: MUSCLE Question

1998-09-29 Thread Walter Franzini
On Tue, Sep 29, 1998 at 09:11:44AM -0500, David Corcoran wrote: > Please answer if you know the following question I'm going to ask. I'm looking I don't know THE answer. This are only my opinions. > now for the best way to make our current resource manager available to > applications. What is t