From owner-freebsd-hackers@FreeBSD.ORG  Thu Oct 23 03:40:37 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 96A3C615
 for <freebsd-hackers@freebsd.org>; Thu, 23 Oct 2014 03:40:37 +0000 (UTC)
Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196])
 by mx1.freebsd.org (Postfix) with ESMTP id 80482F33
 for <freebsd-hackers@freebsd.org>; Thu, 23 Oct 2014 03:40:37 +0000 (UTC)
Received: from u10-2-32-011.office.norse-data.com (unknown [50.204.88.51])
 by elvis.mu.org (Postfix) with ESMTPSA id 4474C341F83D
 for <freebsd-hackers@freebsd.org>; Wed, 22 Oct 2014 20:40:37 -0700 (PDT)
Message-ID: <544878B4.1060804@mu.org>
Date: Wed, 22 Oct 2014 20:40:36 -0700
From: Alfred Perlstein <bright@mu.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Subject: Re: nosh version 1.9
References: <54430B41.3010301@NTLWorld.com> <5443191E.5050208@mu.org>
 <CAJ-VmomhxAkmVpAv5M+h2HiEGnzHuXoZRh=E3LEvcRqbkoJ-5Q@mail.gmail.com>
 <34F30D28-DE9B-444F-885E-F438FEEA46EC@mu.org>
 <CAKYr3zwFyOh0VuQew5XtzKCNe0sDe2qc_5Jg3g9hT8pE7SyhJA@mail.gmail.com>
 <54482A5E.2050303@NTLWorld.com>
 <E03E5E72-6A7E-4206-849D-FFBA35B683A0@turbofuzz.com>
 <CAKYr3zy+H3Fe8L4ZGOmOxzY3byWoOvirQfKeHqeajvR-YvJRVA@mail.gmail.com>
 <527291AC-C5E2-420C-B566-C051BA82CA84@turbofuzz.com>
In-Reply-To: <527291AC-C5E2-420C-B566-C051BA82CA84@turbofuzz.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Oct 2014 03:40:37 -0000


On 10/22/14 7:49 PM, Jordan Hubbard wrote:
>> On Oct 22, 2014, at 7:16 PM, Outback Dingo <outbackdingo@gmail.com <mailto:outbackdingo@gmail.com>> wrote:
>>
>> Actually our port is "very" xml aware :) see https://github.com/outbackdingo/launchd_xml/tree/master/launch_xml <https://github.com/outbackdingo/launchd_xml/tree/master/launch_xml>
> OK, well, launchd as originally designed certainly was not (and is not) xml-aware.  This was on purpose.  You don’t want a lot of surface area in pid 1, which can never crash, nor do you want to bake your serialization format into stone tablets.
>
> launchctl(1) does all the XML parsing and then passes the results to launchd using its own custom IPC format.  Was there some particular reason you violently inserted the XML parsing directly into launchd after the original architect(s) went to such pains to avoid such blatant penitentiary experiences? :-)
>
I could see the utility of that.  One of our senior full stack devs says 
that XML is "triggering" and that they wouldn't want to work on such a 
system.  Perhaps it's to keep web people out?

-Alfred