An asynchronous start up sequence is significantly more trivial to implement then writing a wrapper for gzipSync
On Wed, Apr 18, 2012 at 10:12 AM, Axel Kittenberger <[email protected]>wrote: > 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 > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
