The proxy pattern.
The decorator pattern.
Proxies & Decorators are patterns that abstract away or enhance certain functionality in an entiry.
Since they are both almost the same, it isn't very helpful to know the finer differences between the two, but here they are just for completeness.
Example of a Proxy:
When you proxy some functionality, you generally delegate the responsibility to someone else. The most practical example is an HTTP Proxy that forwards requests on your behalf to the real web-server.
Example of a Decorator:
When you decorate some functionality, you generally add more functionality to it. For this example, I shall discuss the code that is presented below. It is basically an EventEmitter that transparently decompresses the string that is passed to it and re-raises the events that the original EventEmitter raised. You can use it to transparently read a compressed/secure stream given that you have a decorated EventEmitter for it.
File: gzip.js
File: test.js
The decorator pattern.
Proxies & Decorators are patterns that abstract away or enhance certain functionality in an entiry.
Since they are both almost the same, it isn't very helpful to know the finer differences between the two, but here they are just for completeness.
Example of a Proxy:
When you proxy some functionality, you generally delegate the responsibility to someone else. The most practical example is an HTTP Proxy that forwards requests on your behalf to the real web-server.
Example of a Decorator:
When you decorate some functionality, you generally add more functionality to it. For this example, I shall discuss the code that is presented below. It is basically an EventEmitter that transparently decompresses the string that is passed to it and re-raises the events that the original EventEmitter raised. You can use it to transparently read a compressed/secure stream given that you have a decorated EventEmitter for it.
File: gzip.js
var compress = require('compress'); function _inflater(stream) { this._stream = stream; var self = this; var gunzip = new compress.Gunzip; gunzip.init(); this._stream.on('data', function(d) { var _d = gunzip.inflate(d.toString('binary'), 'binary'); self.emit('data', _d); }) .on('end', function() { self.emit('end'); }) .on('error', function() { var args = Array.prototype.splice.call(arguments, 0); args.unshift('error'); self.emit.apply(self, args); }); } _inflater.prototype = new process.EventEmitter(); function _deflater(stream) { this._stream = stream; var self = this; var gzip = new compress.Gzip; gzip.init(); this._stream.on('data', function(d) { var _d = gzip.deflate(d.toString('binary'), 'binary'); self.emit('data', _d); }) .on('end', function() { self.emit('end'); }) .on('error', function() { var args = Array.prototype.splice.call(arguments, 0); args.unshift('error'); self.emit.apply(self, args); }); } _deflater.prototype = new process.EventEmitter(); exports.inflater = function(stream) { return new _inflater(stream); }; exports.deflater = function(stream) { return new _deflater(stream); };
File: test.js
var gz = require("./gzip.js"); var http = require("http"); var req = http.request({ host: "duckduckgo.com", port: 80, path: "/" }, function(response) { console.log("response headers:", response.headers); // // We check if we need to create a proxy event emitter that // inflates data on the go. // if (response.headers['content-encoding'].search('gzip') != -1) { // // The response object is now the proxy object. A similar // technique is used to support TLS encrypted sockets too. // We just wrap up the original EventEmitter instance in // a proxy instance that does its magic. // response = gz.inflater(response); } response.on('data', function(d) { console.log("Got:", d.toString()); }); }); req.setHeader("Accept-Encoding", "gzip"); req.end();
3 comments:
Boy! You are on a blogging spree! Is this post about how to implement these patterns in node? Some more explanation / code annotation would be helpful!
Yes, these are about node.js
Ah! Shall add more comments next time around...
:D thanks
Post a Comment