From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A0CCA13877A for ; Mon, 11 Aug 2014 19:54:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EDBE6E0A44; Mon, 11 Aug 2014 19:54:22 +0000 (UTC) Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8EC6FE09F5 for ; Mon, 11 Aug 2014 19:54:21 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id u10so6333850lbd.35 for ; Mon, 11 Aug 2014 12:54:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:to:subject:in-reply-to:references :mime-version:content-type; bh=OV0+BD2JjCzCRfqvCWdJ0KiQh4yVgN+YiodJ5/SqbtQ=; b=mi76aHHYbSNOHW0CZyv1XoTX9kNJNmHDUjp9PVWA+cXJAz4popiAzieT+oDaoGMnch JraWwujznQuc3ws4ETA4tRhwldlRzz0c6+5r0AshBP7f03xmMg3JwmzLuk5FQG95faJR 5sFfmIWbI52g6KAFCAhRczQsomXYm8hkt02fWRL1nh3ASxXlfF+rSVmdMX23GaSUN+9G hIrcbLnLscrZISkJjBl3JWbTE7YQR7cqrjlnJkSjD9DUaq4XzqNBzDs3J+yuwaTuN/Sa HQRKmYVARCU2GaMcakdIWKAUyAbvDX54Vl/JObLOJ3yRjPrwn5Nig5Fl92BCQE7F67Ka /eAw== X-Received: by 10.112.62.132 with SMTP id y4mr3476701lbr.105.1407697369612; Sun, 10 Aug 2014 12:02:49 -0700 (PDT) Received: from [192.168.60.64] (office.healtech.ru. [89.208.21.2]) by mx.google.com with ESMTPSA id xk7sm4968606lac.10.2014.08.10.12.02.48 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 10 Aug 2014 12:02:48 -0700 (PDT) Message-ID: <53e7c1d8.07f5980a.1799.6580@mx.google.com> X-Google-Original-Message-ID: <766202221.20140810230247@gmail.com>> Date: Sun, 10 Aug 2014 23:02:47 +0400 From: Igor X-Priority: 3 (Normal) To: Kent Fredric Subject: Re: [gentoo-dev] A constructive reommendation on stablity improvemt In-Reply-To: References: <53e649e6.c8a1980a.2941.4762@mx.google.com> <53e66536.240d700a.104a.477d@mx.google.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----------04F04917C05B7924F" X-Archives-Salt: 024e6e9c-e3ef-4549-b018-8d098e73f1a5 X-Archives-Hash: 406ee8f13e79a261e0ded8d83176cec9 ------------04F04917C05B7924F Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 b= efore it's designed.=20 If you have 1000 requests/second JSON parsing might be a problem and might = require different=20 solutions/hardware.=20 If portage implements data the way it sees is - bad or good - that would re= duce uncertainty and=20 allow tools implemented. OK, let's have another year for everyone to think over it. On 10 August 2014 06:15, Igor 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 -=20 it's Apache web server.=20 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 d= ata about state. This requires the data to have a defined format, and potentially a versioni= ng scheme for that format. And not just a defined format, like JSON for instance, but a defined struct= ure 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. --=20 Kent=20 KENTNL - https://metacpan.org/author/KENTNL --=20 Best regards, Igor mailto:lanthruster@gmail.com ------------04F04917C05B7924F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Re: [gentoo-dev] A constructive reommendation on stablit= y improvemt 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 b= efore 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 re= duce uncertainty and 
allow tools implemented.

OK, let's have another year for everyone to think over it.

On 10 August 2= 014 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 d= ata about state.

This requires the data to have a defined format, and potentially a versioni= ng scheme for that format.

And not just a defined format, like JSON for instance, but a defined struct= ure 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                   &= nbsp;