Re: [tap] Bikeshed: TAP document vs. TAP stream

Salve J Nilsen <sjn@pvv.org> Fri, 05 March 2010 15:19 UTC

Date: Fri, 05 Mar 2010 16:19:03 +0100
From: Salve J Nilsen <sjn@pvv.org>
To: Shlomi Fish <shlomif@iglu.org.il>
In-Reply-To: <201003030026.48203.shlomif@iglu.org.il>
Message-ID: <alpine.DEB.1.00.1003051618390.2167@decibel.pvv.ntnu.no>
References: <alpine.DEB.1.00.1003021642090.2167@decibel.pvv.ntnu.no> <D3EE5777-B71C-48C8-86D4-C8D5BB72C403@hexten.net> <201003030026.48203.shlomif@iglu.org.il>
User-Agent: Alpine 1.00 (DEB 882 2007-12-20)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: tap@ietf.org
Subject: Re: [tap] Bikeshed: TAP document vs. TAP stream
Precedence: list

Shlomi Fish said:
> On Tuesday 02 Mar 2010 23:26:15 Andy Armstrong wrote:
>> On 2 Mar 2010, at 15:52, Salve J Nilsen wrote:
>>> So, what do people think? Should the TAP spec use "stream" instead of
>>> "document" where "document" is used now?
>>
>> stream++
>>
>> Maybe there'd be a context in which one would want to refer to a TAP
>> document but stream should be the default I think.
>
> +1 to stream++ too.

Ok, I've updated the wiki text with this now. :)


- Salve

-- 
#!/usr/bin/perl
sub AUTOLOAD{$AUTOLOAD=~/.*::(\d+)/;seek(DATA,$1,0);print#  Salve Joshua Nilsen
getc DATA}$"="'};&{'";@_=unpack("C*",unpack("u*",':4@,$'.#     <sjn@foo.no>
'2!--"5-(50P%$PL,!0X354UC-PP%/0\`'."\n"));eval "&{'@_'}";   __END__ is near! :)

[tap] Bikeshed: TAP document vs. TAP stream Salve J Nilsen
Re: [tap] Bikeshed: TAP document vs. TAP stream Ovid
Re: [tap] Bikeshed: TAP document vs. TAP stream Andy Armstrong
Re: [tap] Bikeshed: TAP document vs. TAP stream Shlomi Fish
Re: [tap] Bikeshed: TAP document vs. TAP stream Salve J Nilsen
Re: [tap] Bikeshed: TAP document vs. TAP stream Aristotle Pagaltzis