> What does that mean? When the handler is invoked, what does it see?
>
> $fh = open myhttp "http://www.perl.com", "fred", "barney";
>
> Does that result in a call like this?
>
> myhttp::open("http://www.perl.com", "fred", "barney");
Exactly. Or to be "more correct"
myhttp->open("http://www.perl.com", "fred", "barney");
> Why strip anything? Just pass the string to the handler verbatim. It
> would certainly seem weird to me if URI-handlers got something
> different than other special-purpose handlers.
>
> <imagine>
> http::open("www.perl.com", "fred", "barney"); # weird
> myhttp::open("http://www.perl.com", "fred", "barney");
> </imagine>
That's fine by me. I'm going to put out an RFC today on embedding full
URI support, since nobody has yet. We can discuss this more then.
> > If no handler by that name has been
> > registered, undef is returned.
>
> Where are these handlers registered? How are they registered? In my
> mind I was thinking that we could just name our handlers as packages
> so that
>
> $fh = open "http://www.perl.com"; # and
> $fh = open myhttp "http://www.perl.com";
>
> would cause Perl to search @INC for http.pm and myhttp.pm and auto-use
> them.
Basically, you're right. I'll have an RFC out later today on handlers
and pseudo-classes. A handler is just >= 1 class. The RFC on AUTOLOAD
being able to decline a request? Same idea. Think Apache handler. All
will become "clear" soon... :-) :-) :-)
-Nate
