[JDEV] MIME, was My evil plans for a client.

[arh14 at cornell.edu]

Sorry if I appear to be carping on about MIME, but this would be the 
case in which it would help.  The client would know what type of file it 
was, and then act accordingly, perhaps passing it on to a plugin.  For 
instance, text/plain could by default be handled internally by popping up 
a dialog with the message in it.  Somehow the info about what type of 
file it is, or how it is encoded needs to be stored somewhere.  Instead 
of relegating this to individual transports (which themselves are not 
necessarily tied to an encoding), or some new method of specification in 
the Jabber protocol, I am simply offering the suggestion that MIME be used.

I realize that this may be totally orthogonal to the other discussions at 
hand.

Aaron

On Mon, 9 Aug 1999, Thomas D. Charron wrote:

> On Mon, 9 Aug 1999 13:15:19    arh14 wrote:
> >Just a question...when you recieved the file at the endpoint, how did the 
> >client know what "type" of file it was?  Is this specified in the Jabber 
> >protocol, or in uuencode...?
> 
>   Didn't matter..  It simply ssaved it off to a directory..  It wasn't very mature, merely dabblings in expanding the <ext> tags.. ;-P
> 
> ---
> Thomas Charron