From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.229.201.42 with SMTP id ey42csp11160qcb; Sun, 15 Apr 2012 23:41:51 -0700 (PDT) Received: by 10.52.27.69 with SMTP id r5mr4367723vdg.129.1334558509215; Sun, 15 Apr 2012 23:41:49 -0700 (PDT) Return-Path: Received: from mail-vb0-f59.google.com (mail-vb0-f59.google.com [209.85.212.59]) by mx.google.com with ESMTPS id z8si906255vcw.77.2012.04.15.23.41.41 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 15 Apr 2012 23:41:49 -0700 (PDT) Received-SPF: pass (google.com: domain of rack-devel+bncCNv1-4HVAxCl_q78BBoEFWyfDw@googlegroups.com designates 209.85.212.59 as permitted sender) client-ip=209.85.212.59; Authentication-Results: mx.google.com; spf=pass (google.com: domain of rack-devel+bncCNv1-4HVAxCl_q78BBoEFWyfDw@googlegroups.com designates 209.85.212.59 as permitted sender) smtp.mail=rack-devel+bncCNv1-4HVAxCl_q78BBoEFWyfDw@googlegroups.com; dkim=pass header.i=@googlegroups.com Received: by vbbfr13 with SMTP id fr13sf4595390vbb.14 for ; Sun, 15 Apr 2012 23:41:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:date:from:to:message-id:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=jOkmstLace2+i2ZachnxmCnS3nIfXtSY794OR17D6MU=; b=v9JPNRyyPc1q3T8tqgmcVF3NsiBioTyy3teMYuQr2V92xtdGjcVenL/f6adNUNRRKZ OGQrWvvQwSS5Ev7nXAGKK2rVm1WzSxtn3bZk7eJpiwrgO5qaeHaaNX/an1XUqmUMgHt3 KrteLFWxLggBaXF40Bl6emW2an1KGm69HL1Gk= Received: by 10.224.73.67 with SMTP id p3mr838150qaj.2.1334558501388; Sun, 15 Apr 2012 23:41:41 -0700 (PDT) X-BeenThere: rack-devel@googlegroups.com Received: by 10.229.111.140 with SMTP id s12ls4118201qcp.4.gmail; Sun, 15 Apr 2012 23:41:39 -0700 (PDT) Received: by 10.224.184.70 with SMTP id cj6mr4752699qab.3.1334558499696; Sun, 15 Apr 2012 23:41:39 -0700 (PDT) Received: by 10.224.203.4 with SMTP id fg4msqab; Sun, 15 Apr 2012 17:41:07 -0700 (PDT) Received: by 10.52.31.42 with SMTP id x10mr614157vdh.7.1334536867476; Sun, 15 Apr 2012 17:41:07 -0700 (PDT) Date: Sun, 15 Apr 2012 17:41:07 -0700 (PDT) From: "P ." To: rack-devel@googlegroups.com Message-ID: <11588923.816.1334536867088.JavaMail.geo-discussion-forums@vbhy13> Subject: Rack asynchronous responses with async.callback MIME-Version: 1.0 X-Original-Sender: pat@polycrystal.org Reply-To: rack-devel@googlegroups.com Precedence: list Mailing-list: list rack-devel@googlegroups.com; contact rack-devel+owners@googlegroups.com List-ID: X-Google-Group-Id: 486215384060 List-Post: , List-Help: , List-Archive: Sender: rack-devel@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary="----=_Part_815_5562815.1334536867086" ------=_Part_815_5562815.1334536867086 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I am doing some work with JRuby that may need asynchronous HTTP support. There doesn't seem to be much documentation about this online, so I did some digging to see how the existing Rack async servers do things, and wrote up some documentation for myself. I thought maybe others would find it useful: http://polycrystal.org/2012/04/15/asynchronous_responses_in_rack.html I also found some posts from a couple years ago implying that 'async.callback' will never be a part of the Rack specification: https://groups.google.com/forum/?fromgroups#!searchin/rack-devel/async/rack-devel/fu58paleLJg/frwK57QHNn4J Is this still the case? I must say I'm a bit disappointed by this discovery, but I don't fully understand all the issues (in particular, my documentation above ignores interaction with middleware). ------=_Part_815_5562815.1334536867086 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable I am doing some work with JRuby that may need asynchronous HTTP support.&nb= sp; There doesn't seem to be much documentation about this online, so I did= some digging to see how the existing Rack async servers do things, and wro= te up some documentation for myself.  I thought maybe others would fin= d it useful: http://polycrystal.org/2012/04/15/asynchronous_response= s_in_rack.html

I also found some posts from a couple years ago i= mplying that 'async.callback' will never be a part of the Rack specificatio= n:

https://groups.goo= gle.com/forum/?fromgroups#!searchin/rack-devel/async/rack-devel/fu58paleLJg= /frwK57QHNn4J

Is this still the case?  I must say I'm a bit= disappointed by this discovery, but I don't fully understand all the issue= s (in particular, my documentation above ignores interaction with middlewar= e).
------=_Part_815_5562815.1334536867086--