search

juju-solutions / interface-http

Interface layer for the basic http interface protocol
4 stars 7 forks source link

This interface should support URLs as the primary format for passing site configuration data. #3

Open spacehobo opened 8 years ago

spacehobo commented 8 years ago

Separating out port, hostname, is-this-SSL flags, etc are useless busywork in a universe where we have URLs. The primary structured data format for the HTTP interface should be nothing but URLs.

A reverse proxy? Two urls: one for the desired front-end, and one for the active back-end.

WSGI charm? Two urls: one for the desired front-end, and one file:/// for the wsgi script itself.

URLs make intuitive sense to us as users of the Web, and they're the only sensible choice for passing site configuration data around. They're self-documenting and complete. And it's not like we don't have urlparse() when we need it!

spacehobo commented 8 years ago

In fact, the interface can give urlparse objects to the receiving side.

marcoceppi commented 8 years ago

Unfortunately this is the interface, one of the first, created almost 5 years ago. Interfaces don't have versions for protocol so if this is insufficient we would need to create a new interface. I've been drafting an email about a new "website" protocol which would allow us to take what we've learned from http and make a more comprehensive interface

merlijn-sebrechts commented 7 years ago

@marcoceppi Any update on the "website" protocol?