[Zlib-devel] Parallel zlib

[Enrico Weigelt]

Hi,


Note that both approaches imply BIG interface changes. Not just in 
the API, but the whole control/data flow. This can not just affect 
semantic stability, but also lead to huge performance problems on 
high loads.

If I think eg. of the my current customer's mass webhosting boxes
(about 3 Mio customers on several hundred boxes) and a zlib now
firing up its own threads, I really get horrified.

zlib should stay as passive as possible, try to circumvent all
non-explicit flows.

Of course, using hw parallelism is good thing. But _please_ make 
a *NEW* library for that. Otherwise we'll be forced to fork :(


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------