In that case, would you like me to commit the code I have? I agree about reworking the stream implementation. The existing code could be written as a number of filters: gzip, openssl, sparse, block/deblock. With a well defined API you would be able to define new stream types in the configuration files using these filters in addition to external filters located in shared libraries.
-----Original Message----- From: Landon Fuller [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02, 2006 3:38 PM To: Robert Nelson Cc: 'Michael Brennen'; [EMAIL PROTECTED]; bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Encryption/Compression Conflict in CVS On Nov 2, 2006, at 13:22, Robert Nelson wrote: > The problem is that currently there are three filters defined: > compression, > encryption, and sparse file handling. The current implementation of > compression and sparse file handling both require block boundary > preservation. Even if zlib streaming could handle the existing > block based > data, sparse file handling would be broken. That's true. It's also not possible to make it handle streaming. Bummer. Block-preserving it is, then. The stream implementation could really use a refactor, coupled with a more modular filter API, but that's not something I'll have time for anytime soon. -landonf ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
