|
|
|
|
|
|
by chii
1749 days ago
|
|
|
The difference between a file and a message is that a file does not prescribe format of the file - it's usually application dependent, but is understood to be plain text. A "message" tends to have formats associated with it (which is what differentiate it from being just a "file" that's transferred via a protocol). These formats, like JSON, or xml, or whatever new fangled formats kids these days use, now requires architectural astronauting; namely, common field names, or standards, so that different programs would parse them similarly. And now you'd want schemas for those formats, and automatic parser generated for those formats, and more and more... |
|
|
It's not. Plenty of Unix tools work with binary files.
> A "message" tends to have formats associated with it
It doesn't. At least, not any more than a "file" tends to have formats associated with it.