From owner-freebsd-net Sat Jan 30 00:32:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00939 for freebsd-net-outgoing; Sat, 30 Jan 1999 00:32:45 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00932 for ; Sat, 30 Jan 1999 00:32:42 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA09167; Sat, 30 Jan 1999 09:32:08 +0100 (CET) To: Archie Cobbs cc: julian@whistle.com, net@FreeBSD.ORG Subject: Re: netgraph... In-reply-to: Your message of "Sat, 30 Jan 1999 00:22:00 PST." <199901300822.AAA06454@bubba.whistle.com> Date: Sat, 30 Jan 1999 09:32:07 +0100 Message-ID: <9165.917685127@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199901300822.AAA06454@bubba.whistle.com>, Archie Cobbs writes: >Poul-Henning Kamp writes: >> >What did you think of the idea of having each node contain two >> >new methods for encoding and decoding ASCII strings? I say methods >> >but really they would just understand two new generic message types. >> >> I don't see the point, quite frankly... > >The point is that you avoid having to parse ASCII strings >for *every* control message. I simply don't understand why we can't have a single type of controlmessage that means "Here is an ascii string to you from the super-user, do whatever he tells you to, thankyou!" That's what I'm asking for, no more, no less. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message