gnu-crypto-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU Crypto] Cascade Cipher API (long)


From: Raif S. Naffah
Subject: Re: [GNU Crypto] Cascade Cipher API (long)
Date: Thu, 20 Mar 2003 13:54:23 +1100
User-agent: KMail/1.4.3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

On Thursday 20 March 2003 13:33, Casey Marshall wrote:
> Raif S. Naffah wrote:
> | hello there,
> |
> | here is a first cut of the Cascade API, with a proof-of-concept
> | (TestOfCascade).
> |
> | things i'm not sure, or not 100% convinced, about are:
> |
> | * the way to initialise a cascade;
>
> Since a complete Cascade essentially represents a tree, one way would
> be to pass it a Map of Maps. The keys could be unique identifiers
> returned by the append() method, or perhaps allow user-supplied keys
> to be passed to that method.

good idea :-)  i'll think more about it and how to implement it within 
the API.


> | * whether to call the operational state State or Direction;
>
> Either one works, but then again Java is a rather verbose language as
> it is.

i was referring more to the role of this enum class.  Direction projects 
the concepts of orientation, bipolarity, etc. which really is what is 
meant in this case --i tried to visualise this in the diagrams, 
somewhere in the javadocs.

the more i talk about it, the more i find Direction is more appropriate.


> | * there's a real benefit in exposing an IStage interface;
> | * there's a need to implement cloning;
>
> I don't see either of these being of much use.

ok.  i'll get rid of them and will checkin the classes soon.


do you have concrete ideas about the Assembly?  if not i'll start on 
this as soon as i checkin the cascade stuff.


cheers;
rsn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique

iD8DBQE+eS1g+e1AKnsTRiERA+wlAJ46Nnzpf8CgxQ2YIrvrgB2dDTHtjQCfTYbq
YQ/oja4eRYBl0TW/qZEKq2g=
=4BAB
-----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]