Re: Proposal: HTTP_NokiaImageUpload

<mj@php.net> wrote : > On Sun Jul 13, 2003 at 05:3059PM +0200, Bertrand Mansion wrote: >> About making it generic, you will have to send me a few phones, the latest >> generation will do, so I can test my code ;) Seriously, I don't think this >> is feasible because they are all going to have different API (and Image >> Upload is not supported on all phones). > > I guess we could settle with something like "upload containers" where > there is a container for Nokia, one for Siemens etc. This way the API of > each phone is handled inside of the container, while the main class > exposes a generic API for the user. > > Having a container for Nokia will be a good start and I'm pretty sure > that there will be other people joining you with support for more > phones. I don't want to spend too much time on this package. I have already developed the main class, along with a container for PEAR DB and another one for a photo gallery software and it just works. At the moment, I don't think other phones manufacturers have an image upload API available. So I don't see why I would figure out a abstraction for something that don't even exist. Furthermore, your proposal reminded me the saying "Why make it easy when it can be made difficult ?" It seems that it is now the way to go in PEAR. I don't think it's a good idea. I am not saying that packages should not interoperate, but the less dependency they have, the better. Usability and lightness should be favored instead of trying to make "Swiss army knives" classes. Bertrand Mansion Mamasam