At 9:36 AM -0700 4/26/97, John C Klensin wrote:
> application/MARC; OID="1.2.840.10003.5.nnn"
>or
> application/MARC; Form=aaaaaaaa
...
>or those could actually be combined or made alternatives in
>a single registration. That isn't something I'd
It occurs to me that one additional item of information might be
helpful in your (general, plural your) deciding on how you (g,py) want to
make this choice, and that has to do with the handling of content-type
strings versus the handling of mime parameters. The bulk of Mime
environments dispatch to the content-aware application based solely on the
content-type/subtype string. That is, they do not use any additional
parametric information to make the dispatching decision.
If these different OID-related sub-types actually are likely to be
processed by different applications, it would be best to have the
distinguishing detail present in the Mime content type/subtype string,
rather than in the parameter string. Otherwise, there will need to be a
generic sub-switch that is called by the Mime processor and then has the
job of looking at the parameter, to determine the actual application to
invoke. This latter approach is, of course, highly suboptimal.
d/
--------------------
Dave Crocker +1 408 246 8253
Brandenburg Consulting fax: +1 408 249 6205
675 Spruce Dr. [log in to unmask]
Sunnyvale CA 94086 USA http://www.brandenburg.com
Internet Mail Consortium http://www.imc.org, [log in to unmask]
|