-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Nienberg wrote:
> Thanks, I'll have a look. Was it decided to leave the encoding the way > it is for backward compatibility or will it eventually be done in the > standard way? I don't think anything was actually decided; consensus seemed to be that the current code has to remain there for backwards compatability, but that a fixed version can be used when all elements concerned know how to do the fixed version. > Mark - -- Chris Crowther -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEZEFxz8bl0gyT/hERAmsMAJ0XJrgmQNK66xOXlkYfoh9GDKc6VgCeLJz3 gC/VwyjHXR2BLbHBBT77gjA= =GqmD -----END PGP SIGNATURE----- ------------------------------------------------------- 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