content types within the WWW library

montulli@stat1.cc.ukans.edu (Lou Montulli)
From: montulli@stat1.cc.ukans.edu (Lou Montulli)
Message-id: <9308172218.AA27390@stat1.cc.ukans.edu>
Subject: content types within the WWW library
To: www-bug@nxoc01.cern.ch
Date: Tue, 17 Aug 93 17:18:19 CDT
Cc: www-talk@nxoc01.cern.ch
X-Mailer: ELM [version 2.3 PL2]
Status: RO
This is a message pertaining to the WWW Library.  If you arn't using
the library or are not familiar with it, just ignore it.


In HTInit.c there are ways to set up the stream type for FTP using
file extensions.  Using HTSetSuffix the stream type can be defined
as binary, 7-bit, or 8-bit.  This is good!  What isn't good is that
there is no way to specify the stream type for HTTP file transferes.
HTSetConversion allows you to set the procedure used for the conversion
but says nothing about whether to transfer the file in binary, 7-bit or
8-bit.  I think some other routine needs to be created to specify
uniquely the transfer type for each MIME type.  Seperate this designation
from HTSetSuffix and specify globaly the transfer type for each content
type.  I suggest HTSetTransferType with minimum arguments of
MIME_TYPE and TRANSFER_TYPE, where MIME_TYPE is any mime type and
TRANSFER_TYPE is one of binary, 7-bit, or 8-bit.

:lou
-- 
  **************************************************************************
  *           T H E   U N I V E R S I T Y   O F   K A N S A S              *
  *         Lou  MONTULLI @ Ukanaix.cc.ukans.edu                           *
  *                         Kuhub.cc.ukans.edu      ACS Computing Services *
  *     913/864-0436        Ukanvax.bitnet             Lawrence, KS 66044  *
  *             UNIX! Cool! I know that!  Jurassic Park - The Movie        *
  **************************************************************************