[BEEPwg] SEQ frames and MIME entity headers

Jered Floyd jered@permabit.com
17 Jun 2002 13:00:12 -0400

> That's true, but it doesn't have to.  Applications that depend on that
> feature can define mechanisms in their profiles for doing that.  The
> core profiles don't have any such mechanism, but then-- they don't
> need to send pathologically long entity headers, do they?

Applications can only define mechanisms in their profiles only if 
their profiles are tied to only operate over a TCP transport.  This
seems poor.  The core profiles don't need to send 'pathologically'
long entity headers, but they *could*, and changing the standard
in such a way where the 'proper' behaviour can only be defined as
'deadlock' is inappropriate.  It's reasonable to disallow certain
operations, but only if failure can be indicated meaningfully.