owsei@programming.devtoAsklemmy@lemmy.ml•asking lemmy to 'Draw a duck and share your art'
0·
1 month ago
It’s more goose than duck, but I like it. It’s also pretty fat :)
It’s more goose than duck, but I like it. It’s also pretty fat :)
Is it not about chaining processes?
IIRC the ideia was to use pipe (or other methods) to send one program’s output to another’s input
But it very well could be about reusable functions, as code or as a .so file
It may not work directly, but there’s always a way to misdirect it, like a vm!
TCP is the way that you send information, HTTP is what it means.
The difference, in your case, is the port. You
can’tCAN have TCP and UDP on the same port, but you can’t have the same protocol on the same port.edit: I didn’t knew you could have different transfer protocols on the same port, ty!