Emulates Node's zlib module for Browserify using pako. It uses the actual Node source code and passes the Node zlib tests by emulating the C++ binding that actually calls zlib.
The following options/methods are not supported because pako does not support them yet.
params
methoddictionary
optionMIT
# browserify-zlib Emulates Node's [zlib](http://nodejs.org/api/zlib.html) module for [Browserify](http://browserify.org) using [pako](https://github.com/nodeca/pako). It uses the actual Node source code and passes the Node zlib tests by emulating the C++ binding that actually calls zlib. [![browser support](https://ci.testling.com/devongovett/browserify-zlib.png) ](https://ci.testling.com/devongovett/browserify-zlib) [![node tests](https://travis-ci.org/devongovett/browserify-zlib.svg) ](https://travis-ci.org/devongovett/browserify-zlib) ## Not implemented The following options/methods are not supported because pako does not support them yet. * The `params` method * The `dictionary` option ## License MIT
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 19553 | swellard | Move and rename clients | ||
//guest/perforce_software/helix-web-services/main/source/clients/2016.1.0/javascript/node_modules/browserify-zlib/README.md | |||||
#1 | 18810 | tjuricek |
First-pass at JavaScript client SDK. JavaScript requires Node with Gulp to "browserfy" the library. It's the easiest way I found to use the swagger-js project; bundle up a wrapping method. There is no JavaScript reference guide. The swagger-js doesn't really document what they do very well, actually. Overall I'm not particularly impressed by swagger-js, it was hard to even figure out what the right method syntax was. We may want to invest time in doing it better. This required setting CORS response headers, which are currently defaulted to a fairly insecure setting. |