Look into supporting nicer URL syntax of curl-unix-socket

[httpie]

Look into supporting nicer URL syntax of curl-unix-socket

[jkbrzt]

Sounds good, anything needed from HTTTPie?

[msabramo]

@jkbrzt: Question: Is it possible for an HTTPie transport plugin to support multiple prefixes? E.g.:

class UnixSocketTransportPlugin(TransportPlugin):
    name = 'UNIX socket transport'

    prefix = ['http://sock.local/', 'http+unix://']

    def get_adapter(self):
        return UnixAdapter()

Because I have a new scheme that I'm playing with, but I thought it would be nice to support the old prefix too. Though maybe I shouldn't worry too much about it, since the version number is < 1 and thus arguably, people should be willing to accept breaking changes.

[jkbrzt]

@msabramo the plugin API currently only supports one prefix per plugin. But you could, for example, expose two plugins (differing only in the prefix) in setup.py, e.g.:

    entry_points={
        'httpie.plugins.transport.v1': [
            'httpie_unixsocket = httpie_unixsocket:UnixSocketTransportPlugin',
            'httpie_unixsocket_legacy = httpie_unixsocket:LegacyUnixSocketTransportPlugin',
        ]
    },

[graingert]

you can't use sock.local

".local" is the domain used to advertise with multicast DNS.

you need to use a subdomain of your own domain name.

[msabramo]

@jkbrzt: Thanks! Yeah that's what I was starting to think of as well after I posted my comment. Not a bad option. Although I might end up not needing it, because folks seem to be wanting to keep the http+unix:// protocol, in which case I could get by with just one plugin object.

[msabramo]

Note: I have begun working on this in msabramo/requests-unixsocket#34

[msabramo]

Thanks, @graingert! Yeah a few people have mentioned that; I wasn't aware that .local has special meaning; good to know! And I see you found and commented on msabramo/requests-unixsocket#34, which is great, because that's where all that discussion is happening.