
Product
Rust Support in Socket Is Now Generally Available
Socket’s Rust and Cargo support is now generally available, providing dependency analysis and supply chain visibility for Rust projects.
jitpc is a module for creating cross-platform ipc servers / clients
npm i --save jitpc
See /example for detailed example.
const client = jitpc.connect(id, [options])connect returns a JSON rpc instance. id is a
unique string representing the ipc server to connect to.
const id = 'id-of-my-ipc-sever'
const client = jitpc.connect(id)
await client.request('hello', 'world')
Options include:
{
async spinup () {} // a function that gets called if the client cannot connect to the server
// useful for spinning up a server if none exists
}
Note that when the client has nothing to do, ie no pending requests and no responders attached, it will auto unref itself, to avoid the process hanging. If a new request is issued, it will auto ref itself as well.
client.userData = dataAssign an object to client.userData to associate state with a client.
client.idFor server clients. ID of the client. Number. 0 for client-side clients instances.
const reply = await client.request(method, params)Send a request.
client.notify(method, params)Send a fire and forget request.
client.respond(method, async function onrequest (params) { ... })Setup a response handler (a responder) that responds to any request against method.
client.unrespond(method)Unregisters the responder to stop responding to a given method.
client.end()Gracefully end the client, ie wait for requests, pending responds to finish.
client.destroy([err])Forcefully end the client.
const server = await jitpc.listen(id, [options])listen returns a Promise that resolves to an EventEmitter or null
if a server is already listening on id. id is a unique string representing
the ipc server.
const id = 'id-of-my-ipc-sever'
const counters = new Map()
const server = await jitpc.listen(id)
server.on('client', (client) => {
client.respond('init', function ({ key }) {
const counter = { count: 0 }
counters.set(key, counter)
return { action: 'ok', payload: { id, count: counter.count} }
})
client.respond('inc', function ({ key }) {
const counter = counters.get(key)
counter.count++
return { action: 'ok', payload: { id, count: counter.count} }
})
})
Options include:
{
async spindown () {}, // a function that gets called before the server is spun down
spindownTimeout: 5000 // the number of milliseconds to wait before closing the server after
// the server opens and doesn't receive any connections OR after the
// number of connections to the server drops to zero
}
server.clientByIdGet a client by given ID. Returns a client or null if no client found. Consider IDs as quick entry IDs.
There is a chance of collision occuring since it is possible for a new client to take up an old ID.
To gaurantee that the client ID matches the expected client, keep an independent counter and match it against a counter in client.userData.
FAQs
just in time ipc servers / clients
We found that jitpc demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Product
Socket’s Rust and Cargo support is now generally available, providing dependency analysis and supply chain visibility for Rust projects.

Security News
Chrome 144 introduces the Temporal API, a modern approach to date and time handling designed to fix long-standing issues with JavaScript’s Date object.

Research
Five coordinated Chrome extensions enable session hijacking and block security controls across enterprise HR and ERP platforms.