Hello Mario, Just one comment: At 06:32 04/08/24 +0200, Mario Salzer wrote:
This vendor tree MIME type registration application discusses the data format emitted by PHPs "serialize()". It is no longer in use only within there; some independent implementations exist (evtl. becoming an exchange format).
Encoding considerations: BINARY
As per current use, contents assigned this MIME Type should be considered to be in the ISO-8859-1 (Latin-1) character set, so that they also may contain arbitrary non-printable characters, binary octets.
Transport channels not capable of handling raw 8 bit without data corruption SHOULD therefore apply a Transfer-Encoding of "base64" or something similar.
Some thought-provoking (hopefully) questions: What are 'arbitrary non-printable characters, binary octets'? Does iso-8859-1 allow the encoding of arbitrary non-printable characters? Does iso-8859-1 encode binary octets? Is it possible in this format to serialize data that is another encoding than iso-8859-1? My advice: Please remove any mention of iso-8859-1 from this draft, it doesn't belong here. Regards, Martin.