er or not
> I will need to give connect() additional params? I'm currently only calling
> it with port after all.
>
>
> Am Mittwoch, 20. Juni 2012 20:21:14 UTC+2 schrieb Ben Kelly:
> So every TCP socket involves two ports; the client port and the server port.
> When
ould
> just be no way to manually change it?
>
>
> Am Mittwoch, 20. Juni 2012 19:21:50 UTC+2 schrieb Ben Kelly:
> Are you saying you want to bind the source port of the TCP socket?
>
> At first glance it does appear that node is lacking an interface to bind a
> socke
Are you saying you want to bind the source port of the TCP socket?
At first glance it does appear that node is lacking an interface to bind a
socket to a specific source port or source address.
On Jun 20, 2012, at 12:46 PM, Fabian Korak wrote:
> Agreed, but for the Echo-algorithm, which identif
There is this:
https://github.com/nearinfinity/node-java
I think it lets you call out to java from node, which is a bit different
than embedding. Not sure if this helps your situation or not.
If you're interested in tight integration with Java, you might also check
out an alternative to node:
thing.
>
> I don't understand how it gets drivers structured, or how it would
> work with nosql databases, but conceptually, it definitely does the
> right thing.
>
> Thanks!
>
> On May 29, 8:59 pm, Ben Kelly wrote:
> > On Tue, May 29, 2012 at 1:40 PM, deitch wro
On Tue, May 29, 2012 at 1:40 PM, deitch wrote:
> a) Is there anything like "rake db:migrate" from Rails for node?
>
One of my coworkers wrote a migration lib for node:
https://github.com/nearinfinity/node-db-migrate
Hope that helps.
Ben
--
Job Board: http://jobs.nodejs.org/
Posting guidel
