Hi, On Tue, Jan 07, 2003 at 12:12:15PM -0800, Sara Golemon wrote: > Speaking of filter "string.base64" I have an issue with its parity. > > string.base64 will encode on write and decode on read... What if the user > wants the other way round? Is the expected behavior even obvious from the > name alone? Should there be two separate filters? string.base64-encode & > string.base64-decode with each doing the same opperation on either read or > write?
Agreed. I hit the same problem you mentioned while implementing iconv encoding conversion filter. I should have made the filters capable of working in the opposite way. But would it rather be preferred to switch the filter function by parameters given to the factory, than to have two similar filters? Then the problem is there's no unified way to handle those parameters. Actually it will do for me to make my own handler, but I see it will definitely end up in great inconsistency. Moriyoshi -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
