Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion How to gzipSync?

Received: by 10.224.173.70 with SMTP id o6mr881806qaz.2.1334740394685;
        Wed, 18 Apr 2012 02:13:14 -0700 (PDT)
X-BeenThere: nodejs@googlegroups.com
Received: by 10.224.95.141 with SMTP id d13ls782153qan.2.gmail; Wed, 18 Apr
 2012 02:12:56 -0700 (PDT)
Received: by 10.224.184.70 with SMTP id cj6mr880629qab.3.1334740376913;
        Wed, 18 Apr 2012 02:12:56 -0700 (PDT)
Received: by 10.224.184.70 with SMTP id cj6mr880628qab.3.1334740376904;
        Wed, 18 Apr 2012 02:12:56 -0700 (PDT)
Return-Path: <axk...@gmail.com>
Received: from mail-qa0-f41.google.com (mail-qa0-f41.google.com [209.85.216.41])
        by gmr-mx.google.com with ESMTPS id b22si10242370qcs.3.2012.04.18.02.12.56
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 18 Apr 2012 02:12:56 -0700 (PDT)
Received-SPF: pass (google.com: domain of axk...@gmail.com designates 209.85.216.41 as permitted sender) client-ip=209.85.216.41;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of axk...@gmail.com designates 209.85.216.41 as permitted sender) smtp.mail=axk...@gmail.com; dkim=pass header...@gmail.com
Received: by qafl39 with SMTP id l39so389878qaf.7
        for <nodejs@googlegroups.com>; Wed, 18 Apr 2012 02:12:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=MvTexs0yKb3pGC7r+dNkPGiUhHlKIM9tl0ar2CKeZdo=;
        b=sua6hgJ3vgz8hE/qpfpd8HN1Xi0MMW5W3HdTQKVglTYj+gsGzE1E3vWXylMTUplrzs
         uPzh1GKus/XbNEztpGmNQOFpFcSDQdNx3F25OMpLe0GdgYr6VXPETOUk3rc4+v2wSBfX
         AFn9UJNJGngrVOMHii0zWt/rcgfXOj0WRTeyFXFuVpHPbzSjVAmCVLs+Cw+yj7EMO3nn
         JESeXwind1h/VueTW20r/p+DR3dg2rRPWSrftgDnNQkPEL6KMYK48vlEbTzDszuMXzaR
         dZhOWDYpqqQ+79e1YDV70niH5m9TNvlVm1FdgzoAeDJXG7/g3XIcmce7NKNQWwKZ7Gyk
         eUrA==
Received: by 10.224.215.7 with SMTP id hc7mr2490407qab.29.1334740376771; Wed,
 18 Apr 2012 02:12:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.50.9 with HTTP; Wed, 18 Apr 2012 02:12:36 -0700 (PDT)
From: Axel Kittenberger <axk...@gmail.com>
Date: Wed, 18 Apr 2012 11:12:36 +0200
Message-ID: <CABg07fsHbNpd_QigDjKAkGoqJXs88ciw1UA_4eX4K+v6CVe...@mail.gmail.com>
Subject: How to gzipSync?
To: nodejs <nodejs@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1

Is there some easy way to make yourself a zlib.gzipSync wrapper around
the nodes default callback/pipe interface to zlib? (Without streamline
or fibers)

Its for the server startup sequence where it generates one hugh
javascript file for the client side to download and it keeps it raw as
well gzipped in memory. It does read the files with readSyncFile etc.
So yes I want the node process to be halted until it is done. Its fine
it takes 2 seconds, so please don't argue it could do this or that in
parallel. I also do the other *Sync calls for startup. I just want to
keep that simple please.

- Axel