From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] A constructive reommendation on stablity improvemt
Date: Sun, 10 Aug 2014 07:49:43 +1200 [thread overview]
Message-ID: <CAATnKFB5Ff=AZZAW2EUfMesePt+5EOzYs48cC3obVPSm6c4WrA@mail.gmail.com> (raw)
In-Reply-To: <53e66536.240d700a.104a.477d@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
On 10 August 2014 06:15, Igor <lanthruster@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
[-- Attachment #2: Type: text/html, Size: 1685 bytes --]
next prev parent reply other threads:[~2014-08-09 19:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 16:18 [gentoo-dev] A constructive reommendation on stablity improvemt Igor
2014-08-09 17:42 ` Kent Fredric
2014-08-09 18:15 ` Igor
2014-08-09 19:22 ` Jeroen Roovers
2014-08-09 19:59 ` Kent Fredric
2014-08-10 0:41 ` Tim Boudreau
2014-08-10 18:53 ` Igor
2014-08-10 21:05 ` Thomas Kahle
2014-08-09 19:49 ` Kent Fredric [this message]
2014-08-10 19:02 ` Igor
2014-08-10 21:03 ` Thomas Kahle
2014-08-12 14:13 ` Ian Stakenvicius
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAATnKFB5Ff=AZZAW2EUfMesePt+5EOzYs48cC3obVPSm6c4WrA@mail.gmail.com' \
--to=kentfredric@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox