> If, on the
> other hand, it has
> some modular CGI interface constructor, it should
> not be limited to
> HTML checking because if it limits itself in what it
> is doing, it
> isn't very modular.
It's not limited to any interface, it has a
constructor that creates an object, which in turn can
be configured and then repeatably used to check
strings with HTML that you pass to its method.
So I think "HTML::CGIChecker" is quite an aproppriate
name for it.
The original idea of "CGI::CheckHTML" araised when I
bulit a message board and desperately needed a way to
deny users to break resulting pages by posting
malicious code, javascripts, porn etc, while still
allowing them to use *some* HTML. The first place I
looked for a solution was the CGI area.
Just my 0.02c.
Thanks, Tomas
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
