Announcing an initial release of a wrapper for java.nio.file's classes and
methods.
It's hard to use java.nio.file.* from clojure, and this library makes that
easier.
Instead of rehashing the documentation, I'll just point you at the
repository:
https://github.com/ToBeReplac
Hi,
Presenting a `javax.http.servlet.HttpServlet` for offloading WebSocket
communication onto `core.async` channels:
https://github.com/ToBeReplaced/jetty9-websockets-async
Note that this implements a `WebSocketServlet` using Jetty9 for the
handshakes. The resulting servlet can be used by any
lettercase <https://github.com/ToBeReplaced/lettercase> is declarative case
conversion for Clojure.
This solves the problem of manipulating case when communicating between
different technologies. For example, converting your lisp-cased keywords
into lowercase strings separated by under
ync, could be blocking, could require a UUID it's
looking for a response to, could have a timeout, could have a timeout
function, etc.
What would OTP look like over channels?
-ToBeReplaced
On 08/02/2013 10:16 AM, Marc Hämmerle wrote:
On Erlang: sometimes you *want* to block on a node and wait
lt.
I think if you disallowed nil as a response, then it would be easy to
use a variety of different blocking calls -- wait forever, wait 30
seconds, wait until (f) returns truthy, etc.
-ToBeReplaced
On 08/01/2013 03:36 PM, Cedric Greevey wrote:
On Thu, Aug 1, 2013 at 1:09 PM, <mailto:toberep
data? It feels like a
procedure call is just a data contract. This library would be doing the
job of wrapping up two different queues -- one for outbound requests and
one for inbound responses. It's true that you'd much rather only have the
outbound queue, but sometimes you need
nc. The send-channels provided would be
used as is, and the receive-channels would be used with an additional
channel outside of it to take the responses off and deserialize them before
returning to the user. The transport provider, of course, would be ZeroMQ.
Are there any projects alread
