Flowering Weeds wrote: > > >> >> When thinking about 2.0, I'm having a hard time with the idea of >> pulling apr-util into regular apr. We've got a lot of stuff in >> apr-util that has nothing to do with "Portability". Basically, I see >> apr-util doing one of two types of things: >> >> * common API to access functionality (dbd, ldap, crypto) > > All do know that crypto in Windows is .NET only from now on? > > http://blogs.msdn.com/karinm/archive/2009/01/19/capicom-dll-removed-from-windows-sdk-for-windows-7.aspx > > So will APR crypto be .NET aware from now on too?
If true; we'll likely substitute openssl in APR. Would solve des_crypt as well. But I'm not certain we really care, the primitives below capicom we use, capicom itself we don't. Bill
