From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Status: No, score=-1.4 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 543E62018E for ; Tue, 9 Aug 2016 01:08:58 +0000 (UTC) Received: by mail-oi0-f50.google.com with SMTP id f189so194921892oig.3 for ; Mon, 08 Aug 2016 18:08:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KX0PNu0bHeiIb4H9OV1jBsT/RLaXj7t7gi66TxWu3Uw=; b=VBsgo0qD4aUGRI7V6Yg5aIbPWLI7lo4s/fAeZiax8q+N76/NjoCN8r/EVsMUWmrhlC k4+myEbvXev/hADBd8796LNPb+dIr0vrHEKFx446z3RNWo4bpZUyNEgRKL7fauHwIVz3 XgrTzv+rSEPWGDy2L58OKD2nFdV/FduMfdG5ImEgqTk3nJT0aSffXFzRK5/JnKwNBwXW HNpDbhp9ZAg/RdoGT3lUGmQaI6lZhqSwigB8xGVBUtvzrTxkST5NuabrlxBFrWgtN2Fo ZF85AF1ma4e44gdi59N4Cu+L/EAkegwVO1fqZ/J914vtXKAmyVH2IjniOBx2KD1WAAyW Z/xA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KX0PNu0bHeiIb4H9OV1jBsT/RLaXj7t7gi66TxWu3Uw=; b=ZV94KNUL9Vfj6PkB73mSlKGSTSFMbCud/WYfcgiYR9fBiGGcybKXxVagAvrTDfaCsF 8RJTgt5flvntRMcQvV9FxF2FcGqnFH64qfhWlvF1woWeMStrA1Ii+yfgAxPgDNCs5qP7 a42d2yYrTu6jKGCjO+J86wny+/HL4M4g/9FAcyfjUWbg9vVYaIiIIVn5hrRNEozdvqNa F9y0baAXVDa39vWXhW0XVwt9X91F8ia1UNmMzsXmmuDor4/xIno64nNYxyIV/fnB8Dyg hM4YVjOF5nu9nAlIpJICJBRI5nsZxwGzlMEzmuntBg4+sWishVW0PipKLlKx3S7ut08i 6CYA== X-Gm-Message-State: AEkoousnxXmikOVwHjTW+7sCNGIU+PAri/ww/uoZO2+SI6NeuCyIEq0iJ3akZsJWQvKP5SGs/RKH9TALuTCRtg== X-Received: by 10.157.13.74 with SMTP id 68mr7686238oti.31.1470704937495; Mon, 08 Aug 2016 18:08:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.81.225 with HTTP; Mon, 8 Aug 2016 18:08:56 -0700 (PDT) In-Reply-To: <460032A6-EF75-4930-8447-0F59C7BC3E4E@2be.co.il> References: <58D32D89-4523-436E-8C0E-FA8F4E7AFFB2@plezi.io> <20160806010126.GA7486@dcvr> <202FC1D8-3042-4CBF-9DEA-85D1BEA080F3@2be.co.il> <460032A6-EF75-4930-8447-0F59C7BC3E4E@2be.co.il> From: Sam Saffron Date: Tue, 9 Aug 2016 11:08:56 +1000 Message-ID: Subject: Re: Please join the Rack Specification discussion for `env['upgrade.websocket']` To: Boaz Segev Cc: Michael Fischer , Eric Wong , unicorn-public Content-Type: text/plain; charset=UTF-8 List-Id: For the record Eric, We use unicorn at Discourse to serve concurrent long polls across 100s of hosted forums using hijack with zero issues using https://github.com/SamSaffron/message_bus I am not particularly enthused WebSockets and have blogged about my reservations, in an HTTP/2 world I am less clear about how they fit in except for some very niche uses. If this becomes a core Rack specification and now forces all Rack implementation to carry around websocket framing protocol and epoll/kqueue I would also be less excited. On Sat, Aug 6, 2016 at 5:37 PM, Boaz Segev wrote: >>> Michael said >> Unicorn is a forking webserver, not an event-driven or threaded >> webserver. Whether Unicorn ever supports the proposed standard or >> not, I wouldn't recommend it be used for typical applications that use >> WebSockets, as they usually involve persistent connections. Unicorn >> would quickly run out of worker processes capable of serving such >> connections anyway, so I question whether it's worth delving into the >> dirty details of IO syscalls. > > >>> Eric said >> Sorry, not interested, and definitely not touching centralized >> message boards :> > > > I totally understand and I thank you both for your time. > > -- Bo. >