144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
- **Binary data:** JSON is a text serialization method, and it takes
up the “payload” area of each HTTP request, so there is no
reasonable way to include binary data in the JSON message without
some sort of codec like Base64, for which there is no provision in
the current JSON API. You will therefore find no JSON API for
committing changes to a file in the repository, for example. Other
Fossil APIs such as [`/raw`](/help?cmd=/raw) or
[`/fileedit`](../fileedit-page.md) may serve you better.
- **64-bit integers:** The JSON standard does not specify integer precision,
because it targets many different platforms, and not all of
them can support more than 32 bits. JavaScript (from which JSON
derives) supports 53 bits of integer precision, which may affect how
a given client-side JSON implementation sends large integers to Fossil’s JSON
API. Our JSON parser can cope with integers larger than 32 bits on input, and it
|
|
|
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
- **Binary data:** JSON is a text serialization method, and it takes
up the “payload” area of each HTTP request, so there is no
reasonable way to include binary data in the JSON message without
some sort of codec like Base64, for which there is no provision in
the current JSON API. You will therefore find no JSON API for
committing changes to a file in the repository, for example. Other
Fossil APIs such as [`/raw`](/help/www/raw) or
[`/fileedit`](../fileedit-page.md) may serve you better.
- **64-bit integers:** The JSON standard does not specify integer precision,
because it targets many different platforms, and not all of
them can support more than 32 bits. JavaScript (from which JSON
derives) supports 53 bits of integer precision, which may affect how
a given client-side JSON implementation sends large integers to Fossil’s JSON
API. Our JSON parser can cope with integers larger than 32 bits on input, and it
|