Hello Kent, Saturday, August 9, 2014, 11:49:43 PM, you wrote:
We have a lot of uncertainty even about what to send and how. It is important for a data processor to understand what data is going to be fed before it's designed. If you have 1000 requests/second JSON parsing might be a problem and might require different solutions/hardware. If portage implements data the way it sees is - bad or good - that would reduce uncertainty and allow tools implemented. OK, let's have another year for everyone to think over it. On 10 August 2014 06:15, Igor <lanthrus...@gmail.com> wrote: Communication protocol is already there - it's HTTP, method POST HTTP protocol is already with Python - CURL, WGET A reliable server ready to accept data from portage is all so there - it's Apache web server. For the sake of this discussion, those protocols serve only as a channel. You have to send some kind of data structure over that channel indicating data about state. This requires the data to have a defined format, and potentially a versioning scheme for that format. And not just a defined format, like JSON for instance, but a defined structure of JSON representation with keys and values being clearly stipulated. You can't just send arbitrary freeform JSON to a random server and hope it pulls sense out of fat air. -- Kent KENTNL - https://metacpan.org/author/KENTNL -- Best regards, Igor mailto:lanthrus...@gmail.com
