[BEEPbuilders] Default encoding of a frame's header

[Griffin Caprio]

Huston,

That's what I get for sending an email at 11pm... Upon re-reading it  
this morning, my question made no sense ;)

Thanks for the virtual smack up-side the head.

- Griffin
On Jul 27, 2006, at 8:14 AM, Huston wrote:

> Griffin,
>
> All of the header fields that are defined in the RFC are constrained
> so they can be represented with US-ASCII. The only fields that are not
> explicitly defined in the RFC are the mime headers but I believe they
> are also constrained to US-ASCII in one of the mime RFCs.
>
> --Huston
>
> On 7/26/06, Griffin Caprio <griffincaprio at mac.com> wrote:
>> Hello All,
>>
>> I was wondering if anyone knew what the default encoding should be
>> for a frame's header?  I know that it's ASCII, but I was wondering if
>> it was UTF-8, UTF-16, etc....
>>
>> I couldn't find the answer in the RFC.  All I could find was this
>> paragraph:
>>
>> "  Each frame consists of a header, the payload, and a trailer.  The
>>     header and trailer are each represented using printable ASCII
>>     characters and are terminated with a CRLF pair.  Between the  
>> header
>>     and the trailer is the payload, consisting of zero or more  
>> octets."
>>
>> I took a look at the Java version, and it seems to rely on the
>> platform default. Any help would be appreciated.
>>
>> Thanks,
>>
>> Griffin
>> _______________________________________________
>> BEEPbuilders mailing list
>> BEEPbuilders at lists.beepcore.org
>> http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepbuilders
>>