Stevan Bajić wrote:
...
> Well... since I have different needs for DSPAM I have started some while ago 
> a local fork of DSPAM where I implement stuff that I always wanted to have 
> into DSPAM. One of them is to use fixed length types. I have a local working 
> version that has the exactly same structure on 32/64 bit for the Hash driver. 
> My local version DOES NOT fix the issue with the CSS file from Eric. But what 
> my local version is capable to do is to trigger an error message if the 
> structure is not the way the Hash driver is expecting it. So I don't get a 
> segmentation fault. BUT my local version does not work too with Eric's file. 
> However... I am pretty sure that files created with my local modified Hash 
> driver will not have the issues Eric is reporting. But I really need more 
> testing since I have changed a lot of code and had not enough time to test 
> everything.
>
> You will now for sure ask me to commit those changes. But you know what? It 
> is huge! I almost had to change every file in DSPAM. Commiting something like 
> that would be a huge task. I don't know if this would be okay for the 3.9.x 
> release? And I have not fixed everything nor have I checked all the storage 
> backends. I can say that MySQL driver is working and I can say that the 
> structure of the Hash driver is the same on 32bit and on 64bit. I still have 
> not fixed the endianness of the Hash driver. Next is to work on the 
> PostgreSQL driver and then after that on the SQLite 2/3 dirvers. After that I 
> will go on and fix the endianness of the Hash driver.
>
> My goal is to increase the stability of DSPAM and I need/want the code to be 
> predictable (and currently it is not that much predictable when you look ath 
> the Hash driver). I need a good fundament before I even can think of extendig 
> DSPAM. And I really need to extend it. I must have a good foundation because 
> I want to extend the DLMTP protocol to allow me to decouple the Web-UI from 
> the system where DSPAM is running and I need to add additional features.
>

I'm not 100% sure, but I thing in some (2? 3? years) old post in list 
was noticed some as existing .css files will be corrupted, when 
HashRecMax and/or HashExtentSize dspam.conf values are changed (and 
maybe nor isn't possible convert them to new layout by csscompress). 
When it is true in current dspam versions, then this should be also 
noticed in README or dspam.conf.

Stevan, when you wish, i can help with testing your new code with hash 
driver, when You give me some instruction about it.

Thanks for Your amazing DSPAM work!

Franta Hanzlik

------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Dspam-devel mailing list
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel

Reply via email to