Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #29893
| From | Wayne <nospam@all.invalid> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: java unix domain sockets ... or substitute |
| References | <slrnm0ejqn.fp3.avl@login.logic.tuwien.ac.at> |
| Message-ID | <FkINv.112212$Rp.98491@fx23.iad> (permalink) |
| Organization | Newshosting.com - Highest quality at a great price! www.newshosting.com |
| Date | 2014-09-03 13:36 -0400 |
On 9/3/2014 1:26 PM, Andreas Leitgeb wrote: > I've googled for the terms java unix domain sockets, and it seems like > this cannot be done with plain Java (and its JSL) alone. > > There are a few 3rd party libs (junixsocket & JUDS) which unfortunately > both need native libs, which is a non-starter for me. > > My current approach is to use named pipes intead, where the server > blockingly reads on a "main" pipe (opened just like a plain file). > > Clients first create a new pair of named pipes, and pass the names to > the server, who in response creates a new thread to communicate over > those pipes and serve client's task that way. > > This is somewhat awkward (especially cleaning up of stale named pipes), > and named pipes do not prohibit two readers erroneously on the same pipe. > > I wonder, if there is: > > - a new way to do unix domain sockets in Java (that google doesn't yet > find, or only for non-obvious-to-me keyword). This also includes > solutions that involve execution of standard unix tools, just no JNI. > > - a way to negotiate a bidirectional channel between a client and > the server that doesn't involve creating pipe nodes in the > filesystem. > > The client is non-Java, but otherwise quite flexible. > > I don't want to use inet sockets (not even localhost), because not every > user on that machine should be able to connect, and I don't want to stick > any authorization stuff into the protocol. > Maybe you can create a Java proxy that the non-Java client can use. Then you can use Java messaging (Java EE). A simpler solution may be to use ZeroMQ: <http://zeromq.org/bindings:java> -- Wayne
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
java unix domain sockets ... or substitute Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-09-03 17:26 +0000
Re: java unix domain sockets ... or substitute Wayne <nospam@all.invalid> - 2014-09-03 13:36 -0400
Re: java unix domain sockets ... or substitute Fredrik Jonson <fredrik@jonson.org> - 2014-09-04 07:42 +0000
Re: java unix domain sockets ... or substitute Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-09-04 07:52 +0000
Re: java unix domain sockets ... or substitute Josip Almasi <joe@vrspace.org> - 2014-09-04 09:45 +0200
Re: java unix domain sockets ... or substitute Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-09-04 09:14 +0000
Re: java unix domain sockets ... or substitute Josip Almasi <joe@vrspace.org> - 2014-09-05 10:20 +0200
Re: java unix domain sockets ... or substitute Fredrik Jonson <fredrik@jonson.org> - 2014-09-04 08:34 +0000
Re: java unix domain sockets ... or substitute Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-09-05 01:06 +0000
Re: java unix domain sockets ... or substitute Nigel Wade <nmw@ion.le.ac.uk> - 2014-09-04 11:35 +0100
Re: java unix domain sockets ... or substitute "Chris Uppal" <chris.uppal@metagnostic.REMOVE-THIS.org> - 2014-09-04 15:11 +0100
Re: java unix domain sockets ... or substitute Nigel Wade <nmw@ion.le.ac.uk> - 2014-09-04 15:57 +0100
Re: java unix domain sockets ... or substitute "Chris Uppal" <chris.uppal@metagnostic.REMOVE-THIS.org> - 2014-09-04 16:21 +0100
Re: java unix domain sockets ... or substitute Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-09-05 10:55 +0000
Re: java unix domain sockets ... or substitute (SOLVED) Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-09-05 00:53 +0000
Re: java unix domain sockets ... or substitute (SOLVED) Josip Almasi <joe@vrspace.org> - 2014-09-05 10:23 +0200
csiph-web