| 1 |
Hello Kent, |
| 2 |
|
| 3 |
Saturday, August 9, 2014, 11:49:43 PM, you wrote: |
| 4 |
|
| 5 |
We have a lot of uncertainty even about what to send and how. It is |
| 6 |
important for a data processor to understand what data is going to be fed before it's designed. |
| 7 |
If you have 1000 requests/second JSON parsing might be a problem and might require different |
| 8 |
solutions/hardware. |
| 9 |
|
| 10 |
If portage implements data the way it sees is - bad or good - that would reduce uncertainty and |
| 11 |
allow tools implemented. |
| 12 |
|
| 13 |
OK, let's have another year for everyone to think over it. |
| 14 |
|
| 15 |
|
| 16 |
|
| 17 |
On 10 August 2014 06:15, Igor <lanthruster@×××××.com> wrote: |
| 18 |
Communication protocol is already there - it's HTTP, method POST |
| 19 |
HTTP protocol is already with Python - CURL, WGET |
| 20 |
A reliable server ready to accept data from portage is all so there - |
| 21 |
it's Apache web server. |
| 22 |
|
| 23 |
|
| 24 |
For the sake of this discussion, those protocols serve only as a channel. |
| 25 |
|
| 26 |
You have to send some kind of data structure over that channel indicating data about state. |
| 27 |
|
| 28 |
This requires the data to have a defined format, and potentially a versioning scheme for that format. |
| 29 |
|
| 30 |
And not just a defined format, like JSON for instance, but a defined structure of JSON representation with keys and values being clearly stipulated. |
| 31 |
|
| 32 |
You can't just send arbitrary freeform JSON to a random server and hope it pulls sense out of fat air. |
| 33 |
|
| 34 |
-- |
| 35 |
Kent |
| 36 |
|
| 37 |
KENTNL - https://metacpan.org/author/KENTNL |
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
-- |
| 44 |
Best regards, |
| 45 |
Igor mailto:lanthruster@×××××.com |
Archives