[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-httpd-dev
Subject:    Re: Supporting non-TCP/IP transports
From:       Phil Lello <phil () dunlop-lello ! uk>
Date:       2015-07-20 14:48:36
Message-ID: CAPofZaGFtFwAVXvypUmd=ad8PJKqbVr13uSZ6A+poZJE_wteLQ () mail ! gmail ! com
[Download RAW message or body]

Ignore my last post - presumably UDS is short for UNIX-domain socket!

If we are going down a plugable protocol route, that I'd like to see the
option to use something a lot more complicated that a socket - e.g. a
connection to a remote SSHD / socket forward via libssh or similar.

Phil

On Mon, Jul 20, 2015 at 3:46 PM, Phil Lello <phil@dunlop-lello.uk> wrote:

> Did you mean UDP, or do I need to add UDS to my research list?
>
> On Mon, Jul 20, 2015 at 2:02 PM, Jim Jagielski <jim@jagunet.com> wrote:
>
>> Well, right now httpd (in 2.4) can proxy over UDS... I have
>> been thinking about adding UDS support to Listen as well.
>>
>> > On Jul 18, 2015, at 3:25 PM, Phil Lello <phil@dunlop-lello.uk> wrote:
>> >
>> > Hi all,
>> >
>> > I'm looking at patching httpd/libapr to support non-TCP transports.
>> >
>> > Specifically, the transports I'd like add are:
>> >
>> > - UNIX-domain sockets
>> > - File-system pipes (and pipe-like devices - e.g. serial ports)
>> >
>> > Would there be interest in adding these to core?
>> >
>> > Phil
>>
>>
>

[Attachment #3 (text/html)]

<div dir="ltr"><div><div>Ignore my last post - presumably UDS is short for \
UNIX-domain socket!<br><br></div>If we are going down a plugable protocol route, that \
I&#39;d like to see the option to use something a lot more complicated that a socket \
- e.g. a connection to a remote SSHD / socket forward via libssh or \
similar.<br><br></div>Phil<br></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Mon, Jul 20, 2015 at 3:46 PM, Phil Lello <span \
dir="ltr">&lt;<a href="mailto:phil@dunlop-lello.uk" \
target="_blank">phil@dunlop-lello.uk</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">Did you mean UDP, or do I need to add UDS to \
my research list?<br></div><div class="gmail_extra"><br><div \
class="gmail_quote"><span class="">On Mon, Jul 20, 2015 at 2:02 PM, Jim Jagielski \
<span dir="ltr">&lt;<a href="mailto:jim@jagunet.com" \
target="_blank">jim@jagunet.com</a>&gt;</span> wrote:<br></span><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">Well, right now httpd (in 2.4) can proxy over \
UDS... I have<br> been thinking about adding UDS support to Listen as well.<br>
</span><span class=""><div><div><br>
&gt; On Jul 18, 2015, at 3:25 PM, Phil Lello &lt;<a \
href="mailto:phil@dunlop-lello.uk" target="_blank">phil@dunlop-lello.uk</a>&gt; \
wrote:<br> &gt;<br>
&gt; Hi all,<br>
&gt;<br>
&gt; I&#39;m looking at patching httpd/libapr to support non-TCP transports.<br>
&gt;<br>
&gt; Specifically, the transports I&#39;d like add are:<br>
&gt;<br>
&gt; - UNIX-domain sockets<br>
&gt; - File-system pipes (and pipe-like devices - e.g. serial ports)<br>
&gt;<br>
&gt; Would there be interest in adding these to core?<br>
&gt;<br>
&gt; Phil<br>
<br>
</div></div></span></blockquote></div><br></div>
</blockquote></div><br></div>



[prev in list] [next in list] [prev in thread] [next in thread]