On Wednesday, March 6, 2013 4:37:06 PM UTC-5, Sergey Shteyn wrote:
> How would I make them dependency of main application? Each app module is
> not on npm registry, they are local on the directory.
> mainapp
> package.json
> modA
>package.json
> modB
> package.json
>
> Also modA c
I'm probably stating the obvious here, but if what you need is really just
proxying and routing, are you sure a vanilla HTTP proxy/load-balancer such
as NginX wouldn't do the job?
Writing an http proxy using Node *is* a trivial exercise - took me about an
hour the last time I needed to. But if
The problems Wicket tries to solve (I've coded with Jon Locke who created
Wicket on and off since we were in high-school, and was around for its
creation) are really
- Transparent management of server-side session state using Java
serialization
- Providing an abstraction for per-page and per-c
On Sunday, July 29, 2012 1:22:49 PM UTC-4, Alan Gutierrez wrote:
> The ability to get a patch into the source has given programmers more
> confidence
> in their dependenies. They are no longer deferring decisions by
> "programming to
> interfaces", but instead making a commitment to a dependen
