On Tue, Feb 05, 2019 at 05:01:57AM -0500, Martin Tournoij wrote:
> as soon as you start doing more than printing raw strings.
Not even raw strings, but raw "lines" (\n added by echo).
My 3c.
--
Sylvain
On Tue, Feb 5, 2019, at 21:40, k...@shike2.com wrote:
> >> "My 2c": I would prefer shell "printf" than "echo -n -e"
> >
> > yeah, good point. Any of which works.
>
> Yes, but echo -n is not POSIX.
-n is mentioned, but its meaning is not defined ("defined by
implementation"). -e isn't mentioned
>> "My 2c": I would prefer shell "printf" than "echo -n -e"
>
> yeah, good point. Any of which works.
Yes, but echo -n is not POSIX.
On Mon, 4 Feb 2019 19:56:33 +
sylvain.bertr...@gmail.com wrote:
Dear Sylvain,
> On Mon, Feb 04, 2019 at 08:03:56PM +0100, Laslo Hunhold wrote:
> > echo -n -e "GET / HTTP/1.1\r\nHost: localhost\r\n\r\n" | \
>
> "My 2c": I would prefer shell "printf" than "echo -n -e"
yeah, good point.
Hi Laslo,
04.02.2019, 22:04, "Laslo Hunhold" :
> It is very simple really. Let me give you an example with quark and
> nc(1) (You will need Netcat OpenBSD for the -U flag, which is available
> in all package sources I know).
>
> Let's first fire up quark:
>
> # quark -U uds_main -d .
On Mon, Feb 04, 2019 at 08:03:56PM +0100, Laslo Hunhold wrote:
> echo -n -e "GET / HTTP/1.1\r\nHost: localhost\r\n\r\n" | \
"My 2c": I would prefer shell "printf" than "echo -n -e"
--
Sylvain
On Mon, 04 Feb 2019 18:09:44 +0300
Platon Ryzhikov wrote:
Hey Platon,
> Studying quark commit history i found a note that listening on
> UNIX-domain socket was the idea behind its last rewrite.
this was one reason among others. Most importantly, the "old" quark was
heavily architectured around
Hello!
Studying quark commit history i found a note that listening on UNIX-domain
socket was the idea behind its last rewrite. This led me to the following
questions:
1) how should client be organised to use server in this case?
2) which advantages does it grant and how could they be used?
