Re: HTTP header suggestion/request

> 
> You can develop a complex interrelation - when does Content-Type take
> precedence, when does Content-Disposition?

Appended is what I do.  In brief; trust C-D for storage names,trust
C-T for viewer selection. Im not sure this kind of thing is
appropriate to promulgate in an RFC, though. ANy thoughts?

to generate a filename:
	if C-D provided
		use suggested name
	else
		if C-T has associated suffix
			generate name with appropriate suffix
		else
			dont suggest a name
		endif
	endif

to launch a viewer:
	if c-t has registered viewer
		launch appropriate viewer
	else
		prompt user
	endif
	

	
-Rens