console.log('worker for /pipeHookup/'+req.params.file+' resolves')
res.send({startup:true,ip:ownIp,port:msg.port})
}
})
})
piper.on('error',(err)=>{
piper.on('error',(err)=>{
console.log('worker err',err)
console.log('worker err',err)
})
})
piper.on('exit',(code)=>{
piper.on('exit',(code)=>{
console.log('exit code',code)
console.log('worker exit code',code)
})
})
res.send({address:'localip',port:'1024'})
// then this (or similar) should be all we really need to add here, and we can do local-dev of the pipes in hunks/pipes/pipename.js and pipes/pipename.js
// then this (or similar) should be all we really need to add here, and we can do local-dev of the pipes in hunks/pipes/pipename.js and pipes/pipename.js
// so, do we spawn, or do we use workers ?
// so, do we spawn, or do we use workers ?
// awh yis it's workers, messages easy, errors also OK to catch... nextup: draw the sys, what wraps what doesn't? mostly: want to be able to refresh / reload / restart remotely
// awh yis it's workers, messages easy, errors also OK to catch... nextup: draw the sys, what wraps what doesn't? mostly: want to be able to refresh / reload / restart remotely