port default option

[reqshark]

do we really need another socket option? for sure.

often I find myself using the same TCP port across machines.. thinking it might be nice to specify a socket's default port as part of its initial configuration like maybe:

const pub = require('nanomsg').socket( 'pub', {
  port: 5555,
  tcpnodelay: true,
})

/* now connection argument gets simpler */

pub.connect('tcp://192.168.204.129')
pub.connect('tcp://192.168.204.130')
pub.connect('tcp://192.168.204.131')
pub.connect('tcp://192.168.204.132')
pub.connect('tcp://192.168.204.133')

[yoshuawuyts]

I think this is reasonable.

[reqshark]

cool i'll take that as a plus one

[reqshark]

@yoshuawuyts go for it if u want to PR it, otherwise hopefully I'll have time this weekend to take a swing myself and muster something up here and could probably use your review...

these things all need to be implemented consistently.. i.e. a sockopt also means socket.port(1984)

also i want to address @nickdesaulniers' point in #52, the essence of which seems to be: while testing libnanomsg operational return values confirms library interoperability across calls, nothing else is tested.

[nickdesaulniers]

👍

[yoshuawuyts]

@reqshark happy to review, won't have time to PR it before this weekend