Remove dependency on redis about node-unblocker HOT 5 CLOSED

@emilhem & @mikaelhm - what do you guys think?

from node-unblocker.

I actually don't use redis for my proxy. I started rewriting it for a similar scenario that you describe above but the web server started saying no after I visited a few websites because of the tremendous amount of cookies being sent to the server. Also the overhead of all the cookies will slow everything down quite a lot. Instead I just let the built in session handler in connect handle saving the cookies to the session. It will erase any cookies at server restart but it doesn't matter since the server never dies for me. Our source codes are very different now though since I have user login and an admin interface where you can manage the white-list built in.

I think the idea of making the proxy more independent and modularizable is a good idea. Then you can implement user login/signup and an admin page as well. You're free to use my poorly commented source code if you want.

from node-unblocker.

Instead I just let the built in session handler in connect handle saving the cookies to the session.

Are you only running a single server process? The recommended mode is one process per CPU core (Although it's the same if you have a single-core CPU). Connect's in-memory session handler can't share data across processes which is why I went with Redis initially.

(Sorry if you get this comment twice, github is acting funky)

from node-unblocker.

Yes. I removed the multiprocess functionality. Have you actually made any performance measurements comparing multiprocess vs single process?

from node-unblocker.

This is now done in the 1.0 release. Cookies have their path's scoped to the site and I have a bit of extra code in place to copy cookies over when switching protocol or subdomain. No red is required!

I also made a number of other changes in the vein of modularizing things: the proxy is now available as an express-compatible library and you can add your own processing hoooks and remove or reconfigure all of the built in ones.

from node-unblocker.