Packages'name and extensions of PEAR

Hi QA-team, (As I just took part to this very long dev discussion about HTTP_Cache) It's coming on a question about naming and extending. This HTTP_Cache proposal produces a good example. Obviously, as it intends to do some client side dedicaced caching thru ETags headers, it has to be related to HTTP_Header located in pear/HTTP/Header.php Unfortunately HTTP_Header restrict its caching to Last-Modified in subpackage pear/HTTP/Header/Cache.php Stephan who proposes ETag caching could like to furnish something like this existing pear/HTTP/Header/Cache.php but related to ETag. That could be pear/HTTP/Header/ETag.php Is it possible for him to propose a package HTTP_Header_ETag as it should exactly land in pear/HTTP/Header/ETag.php but should only be an extend of basic HTTP_Header class ? (and not belonging to HTTP_Header) Hope you can understand this ! à+ -- bertrand Gugger (toggg)