This is a valid concern George, and I thought hard about this when I did the NNTP cleanup. My thinking is this: We had a few "hard coded" cases to handle NNTP, FTP and a few other "streaming" protocols (which we'll also need to cleanup next . This limited what a plugin could implement / use from the core to only those few protocols.
By removing this entirely from the core, we'll have to rethink how a plugin would implement new handlers. There will without doubt have to be lots of changes into the core, and additions to InkAPI, but I'm convinced this is the right way to go. Let the plugin register protocols, additions to "logs" and cache and stats, all via well defined APIs in InkAPI. No more hardcoding "cases" into the core, lets fix it when we need this support once and for all.
I hope that makes sense?