Aleph Google Group

Re: Status of SSL support

ret...@gmail.com (Hunter Kelly) — Mon, 13 May 2013 16:41:55 UT

Hi, just wondering if these changes were ever merged in?
I'm looking at the possibility of writing a testing server which accepts
messages in different formats, such as APNS, GCM, etc. APNS uses SSL over
TCP.
I'd like to write the server using Aleph (which looks very nice for what I
need to do) without having a separate proxy server (such as stud) if at all

Re: Enqueing http-request's response body as the response body of the current request

marcin.ku...@gmail.com (Marcin Kulik) — Thu, 09 May 2013 09:45:13 UT

Hey Zach,

Here's an asciicast showing this all in action: [link]

First 2 requests go directly to python's SimpleHTTPServer, one returns 200,
the other 404. Note that in both cases python's server closes the
connection.
Another 2 requests go via aleph's proxy, again one returns 200, the other

Re: problem receiving big map through aleph.object

ztell...@gmail.com (Zach Tellman) — Thu, 09 May 2013 03:54:36 UT

Hey Matthew,

I've never used aleph.object to transmit more than trivial data structures;
while Java serialization is supposed to work on arbitrary data structures,
I'm not sure how true that is in practice. Since this is just a very thin
shim over Java serialization, the sad fact is that it either works or it

problem receiving big map through aleph.object

mathn...@gmail.com (Matthew Chadwick) — Thu, 09 May 2013 02:07:50 UT

I'm using aleph.object to transmit things. I have a client and server
exactly the same as the example code, but with another channel into which I
siphon the channel from the client. I can send objects (Clojure data
structures and Java objects like joda datetimes) just fine. But, the data
structure I want to transmit, a huge clojure.lang.PersistentHashMap of

Re: Enqueing http-request's response body as the response body of the current request

ztell...@gmail.com (Zach Tellman) — Wed, 08 May 2013 20:37:36 UT

I'm a little confused, here. You're creating a proxy, and just returning
the response from the http-request you made. If the body of that response
isn't closing, it's because the server you're proxying to hasn't closed it.
Do you see the same behavior when you directly request from the servers,

Re: Enqueing http-request's response body as the response body of the current request

marcin.ku...@gmail.com (Marcin Kulik) — Wed, 08 May 2013 18:30:38 UT

And curl/httpie doesn't close the connection itself when requesting via my
aleph-based proxy because aleph returns "Transfer-Encoding: chunked "
header.

Any ideas how to solve this issue?

Re: Enqueing http-request's response body as the response body of the current request

marcin.ku...@gmail.com (Marcin Kulik) — Wed, 08 May 2013 18:17:41 UT

Follow up on the issue:

I found out that the channel isn't closed only for some requests. One
example is locally running Rails application - all responses don't trigger
closing of the channel. The other example is "python -m SimpleHTTPServer",
200 responses trigger closing of the channel, 404 responses don't.

Re: Enqueing http-request's response body as the response body of the current request

marcin.ku...@gmail.com (Marcin Kulik) — Wed, 08 May 2013 16:44:22 UT

Hey Zach!

Thanks for quick response. Well it turned out that passing result channel
directly to enqueue was working (to some degree).
I was using httpie tool instead of curl for some of my tests and httpie was
buffering the whole response in order to syntax highlight the whole html.
When I use curl then it correctly displays the whole response (it has

Re: Enqueing http-request's response body as the response body of the current request

ztell...@gmail.com (Zach Tellman) — Wed, 08 May 2013 15:48:29 UT

Hi Marcin,

This is just a guess, but curl doesn't flush the body until there's a
newline or the request is complete. If your chunks don't have newlines,
then it will seem as if nothing's coming in, when really curl is just
holding onto them until it can flush.

As to why lazy-channel-seq doesn't print anything, you shouldn't do

Enqueing http-request's response body as the response body of the current request

marcin.ku...@gmail.com (Marcin Kulik) — Wed, 08 May 2013 09:37:39 UT

I'm trying to write an HTTP proxy that proxies to the proper upstream host
based on the Host header.
Right now I have hardcoded upstream host to localhost:3000.
What I want to achieve is to pass the response body channel from the
http-request
as a response body of the current request. I have the following code:

Re: Testing websockets app in isolation

sid.kur...@gmail.com (Sid Kurias) — Fri, 03 May 2013 05:54:39 UT

Zach,
I have tried to outline my thought process with some drawings. The ascii
art does not look too good. I have attached png for the same.
I think the current documentation is certainly much better. If I were
coming to
Aleph now - for the first time - I would find it a lot easier to understand
the

Re: Testing websockets app in isolation

ztell...@gmail.com (Zach Tellman) — Fri, 26 Apr 2013 22:01:12 UT

Hey Sid,

I agree the "Connections" wiki needed some cleanup. I've made some
changes, I'd appreciate any feedback you can give, in light of your
newfound understanding.

Zach

Re: Testing websockets app in isolation

sid.kur...@gmail.com (Sid Kurias) — Sat, 20 Apr 2013 05:57:27 UT

hmmm....let there be light!!!!
I think your wiki pages are quite well documented. I understood the
semantics behind pipelines and channels after a couple of reads.
It was when I got to Connections that I got confused. I did not understand
how the channel pair worked to give you a bidirectional connection, since

Re: Testing websockets app in isolation

ztell...@gmail.com (Zach Tellman) — Fri, 19 Apr 2013 18:58:31 UT

I'm a little unclear on what you're asking, so let me try to just explain
what's going on another way.

Each channel is two halves, an emitter which creates messages, and a
receiver which accepts messages. In a normal unidirectional channel, these
are the same thing. However, via (splice ...) you can create a channel

Re: HTTP client app hangs on after all work done

ztell...@gmail.com (Zach Tellman) — Fri, 19 Apr 2013 18:41:12 UT

The issue here is that clients share an NioClientSocketChannelFactory [1].
I've pushed a change to 0.3.0-SNAPSHOT which makes those shared threads
daemons, which should fix your issue.

By the way, aleph beta16 already targets lamina beta15, so the exclusions
in your project.clj shouldn't be necessary.