From: Jeff King <peff@peff.net>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: "Heiko Voigt" <hvoigt@hvoigt.net>,
"Git List" <git@vger.kernel.org>,
"Duy Nguyen" <pclouds@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Torsten Bögershausen" <tboegi@web.de>,
"Robert Zeh" <robert.allan.zeh@gmail.com>,
"Erik Faye-Lund" <kusmabite@gmail.com>,
"Karsten Blees" <karsten.blees@gmail.com>,
"Drew Northup" <n1xim.email@gmail.com>
Subject: Re: [RFC/PATCH] Documentation/technical/api-fswatch.txt: start with outline
Date: Tue, 12 Mar 2013 05:55:19 -0400 [thread overview]
Message-ID: <20130312095519.GA12170@sigill.intra.peff.net> (raw)
In-Reply-To: <CALkWK0m+CS25=Z91y90z49g4GK+b7oFugiXoH0h0J6P-yQXRCQ@mail.gmail.com>
On Tue, Mar 12, 2013 at 03:13:39PM +0530, Ramkumar Ramachandra wrote:
> Heiko Voigt wrote:
> > While talking about platform independence. How about Windows? AFAIK
> > there are no file based sockets. How about using shared memory, thats
> > available, instead? It would greatly reduce the needed porting effort.
>
> What about the git credential helper: it uses UNIX sockets, no? How
> does git-credential-winstore [1] work?
No, the main credential protocol happens over pipes to a child process's
stdin/stdout. The credential-cache helper does use unix sockets (since
it needs to contact a long-running daemon that caches the credentials),
and AFAIK is not available under Windows (but that's OK, because
Windows-specific helpers that use secure storage are better anyway).
When I introduced credential-cache, I recall somebody mentioned that
there is some Windows-equivalent IPC that can be used to emulate unix
domain sockets. The calls aren't the same, but as long as your
requirements are basically "get messages to/from the daemon", you can
probably abstract away the details on a per-platform basis.
Unfortunately I can't seem to find the original message or any details
in the archive (and I know next to nothing about Windows IPC).
-Peff
next prev parent reply other threads:[~2013-03-12 9:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 20:17 [RFC/PATCH] Documentation/technical/api-fswatch.txt: start with outline Ramkumar Ramachandra
2013-03-11 17:05 ` Heiko Voigt
2013-03-12 9:43 ` Ramkumar Ramachandra
2013-03-12 9:50 ` Erik Faye-Lund
2013-03-12 9:55 ` Jeff King [this message]
2013-03-12 23:21 ` Karsten Blees
2013-03-13 1:03 ` Duy Nguyen
2013-03-13 17:50 ` Karsten Blees
2013-03-13 19:38 ` Junio C Hamano
2013-03-14 10:58 ` Duy Nguyen
2013-03-15 16:27 ` Pete Wyckoff
2013-03-16 14:21 ` Thomas Rast
2013-03-18 8:24 ` Ramkumar Ramachandra
2013-03-18 10:07 ` Thomas Rast
2013-03-25 10:44 ` Ramkumar Ramachandra
2013-03-25 10:59 ` Duy Nguyen
2013-03-25 11:13 ` Ramkumar Ramachandra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130312095519.GA12170@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=karsten.blees@gmail.com \
--cc=kusmabite@gmail.com \
--cc=n1xim.email@gmail.com \
--cc=pclouds@gmail.com \
--cc=robert.allan.zeh@gmail.com \
--cc=tboegi@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).