From: Stephen D. <sd...@gm...> - 2006-09-18 20:24:16
|
On 9/18/06, Vlad Seryakov <vl...@cr...> wrote: > > > > Because this has never been exposed to Tcl before, and because seems > > to be (to me) a genuine bug which could bight us as we add more HTTP > > 1.1 support, it seems like now would be the time to take a step back > > and look at what we really want in this API. > > > > It's only one call to register, one to unregister, and some Tcl > > wrappers. Do you think it's not worth it? > > > > Ok, what is the new API and logic you want to add? Or i missed it? > I don't know, I'm asking... I was wondering why registering a proxy handler is different than a regular registered proc. Do they have to be different? The main difference seems to be that you can register a proxy for a protocol, i.e. http or https, but you don't have that option with regular registered procs. Is this an important distinction to make though? Registered procs can still check the protocol, manually, if they care. Re having to register for each method, that also is sometimes a problem for registered procs. Maybe allowing something like: ns_register_proc * /* callback Where the only supported symbol is '*', meaning 'default, if no more specific method is registered'. Perhaps that's too confusing -- people will expect full glob support. I don't think glob support is possible, or even desirable here. Url handlers are supposed to be deterministic, only one will match some URL (unlike filters). That's what occurs to me off the top of my head... |