From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-67192-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 3193813877A
for <garchives@archives.gentoo.org>; Sat, 9 Aug 2014 19:49:49 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id E93B1E0A62;
Sat, 9 Aug 2014 19:49:44 +0000 (UTC)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id EA8BBE09D1
for <gentoo-dev@lists.gentoo.org>; Sat, 9 Aug 2014 19:49:43 +0000 (UTC)
Received: by mail-qa0-f51.google.com with SMTP id k15so6548711qaq.38
for <gentoo-dev@lists.gentoo.org>; Sat, 09 Aug 2014 12:49:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=/Yi5Hv8jCPwdjx0/ctnLJK+4NZwEPQRMu0oY6SS1o00=;
b=L/MMCrDa0cn+fh53zAaIxNjAlDVjgHO0PLUuxsj9I6FnRl396GzcrVxefVxtAVp6xQ
B8793Xc2X/g3AA1yG5Ja3pDRfXYEcjMAm947JW1PY2kdjJHqKCIOcguUvuA9/Ey8UNrl
3tIyuj4fTIMefTFK/gj7hEaSkWal/77iLn8cQKfPg2Uy3SytsQCFLgCpiBIf6TrLkLro
sfCa+VTixKbev+/D2LWbu0ZZzOxZBCpYhH8c2M/W4tBO+yj+TzE+xbMA8suqMFY3wbo/
B472e5Ra2g8CJJD5Jbq0guYgl/DOJxIB9dvr/pNLLZUTyQJT1/+bbvrK8rSItbKm2oAB
PCWg==
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.224.137.6 with SMTP id u6mr48598045qat.91.1407613783164;
Sat, 09 Aug 2014 12:49:43 -0700 (PDT)
Received: by 10.140.44.34 with HTTP; Sat, 9 Aug 2014 12:49:43 -0700 (PDT)
In-Reply-To: <53e66536.240d700a.104a.477d@mx.google.com>
References: <53e649e6.c8a1980a.2941.4762@mx.google.com>
<CAATnKFCbc8Hrq2LdGUqswcdXjp63vn2p+aPGa-QyZpKoO-bSuw@mail.gmail.com>
<53e66536.240d700a.104a.477d@mx.google.com>
Date: Sun, 10 Aug 2014 07:49:43 +1200
Message-ID: <CAATnKFB5Ff=AZZAW2EUfMesePt+5EOzYs48cC3obVPSm6c4WrA@mail.gmail.com>
Subject: Re: [gentoo-dev] A constructive reommendation on stablity improvemt
From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Content-Type: multipart/alternative; boundary=001a11c2a3ec86cd540500379f2a
X-Archives-Salt: 8c9f4078-84b1-4ee3-926a-05d9425ed260
X-Archives-Hash: 6d88a216490f86734188eeda509dcf81
--001a11c2a3ec86cd540500379f2a
Content-Type: text/plain; charset=UTF-8
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
--001a11c2a3ec86cd540500379f2a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On 10 August 2014 06:15, Igor <span dir=3D"ltr"><<a href=3D"mailto:lanth=
ruster@gmail.com" target=3D"_blank">lanthruster@gmail.com</a>></span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
<span style=3D"font-family:'Courier New';font-size:10pt">Communicat=
ion protocol is already there - it's HTTP, method POST<br>
HTTP protocol is already with Python - CURL, WGET<br>
A reliable server ready to accept data from portage is all so there -=C2=A0=
<br>
it's Apache web server.=C2=A0</span></blockquote></div><br><br></div><d=
iv class=3D"gmail_extra">For the sake of this discussion, those protocols s=
erve only as a channel.<br><br></div><div class=3D"gmail_extra">You have to=
send some kind of data structure over that channel indicating data about s=
tate.<br>
<br></div><div class=3D"gmail_extra">This requires the data to have a defin=
ed format, and potentially a versioning scheme for that format.<br><br></di=
v><div class=3D"gmail_extra">And not just a defined format, like JSON for i=
nstance, but a defined structure of JSON representation with keys and value=
s being clearly stipulated.<br>
<br></div><div class=3D"gmail_extra">You can't just send arbitrary free=
form JSON to a random server and hope it pulls sense out of fat air.<br><br=
>-- <br><div dir=3D"ltr"><div>Kent<font size=3D"1"><b> <br><br></b></font><=
/div>
<div><span style=3D"color:rgb(204,204,204)"><font size=3D"1"><b>KENTNL</b> =
- <a href=3D"https://metacpan.org/author/KENTNL" target=3D"_blank">https://=
metacpan.org/author/KENTNL</a></font></span><br></div><div><br></div></div>
</div></div>
--001a11c2a3ec86cd540500379f2a--