Neat idea. Perhaps another CacheAccess subclass, or a proxy to an arbitrary CacheAccess, which knows how to filter the elements that pass through it. Then you could register a filter with that access class to encrypt / decrypt items.
My gut feeling is that something like this doesn't belong _in_ the cache, but rather as a wrapper. Putting it in the cache would make an already confusing (CacheAccess/Cache) set of classes more confusing, and add more dependencies, two things I think are already going to be barriers to wider adoption of JCS. -- jt On Fri, 2002-04-12 at 10:44, Aaron Smuts wrote: > I'm thinking of adding a secure put to the cache access that ciphers input > using a passed key. To keep these puts secure the items should never leave > the local vm, but I'm not sure I want to force a local, non spooling > configuration. . . . > > > > Aaron Smuts > Director, Systems and Development > e-Business Division > REALMCash > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > office: (212) 653-0578 > cell: (646) 263-5398 > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
