practical question
Lucas Gonze <lgonze@panix.com> Thu, 24 May 2007 01:20 UTC
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4O1KXRx092078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 May 2007 18:20:33 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l4O1KXfA092077; Wed, 23 May 2007 18:20:33 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l4O1KWlp092058 for <ietf-xml-mime@imc.org>; Wed, 23 May 2007 18:20:32 -0700 (MST) (envelope-from lgonze@panix.com)
Received: from panix2.panix.com (panix2.panix.com [166.84.1.2]) by mail1.panix.com (Postfix) with ESMTP id 9FDAF59684 for <ietf-xml-mime@imc.org>; Wed, 23 May 2007 21:20:31 -0400 (EDT)
Received: from localhost (lgonze@localhost) by panix2.panix.com (8.11.6p3/8.8.8/PanixN1.1) with ESMTP id l4O1KVt24013 for <ietf-xml-mime@imc.org>; Wed, 23 May 2007 21:20:31 -0400 (EDT)
Date: Wed, 23 May 2007 15:20:31 -1000
From: Lucas Gonze <lgonze@panix.com>
Reply-To: lucas@gonze.com
To: ietf-xml-mime@imc.org
Subject: practical question
Message-ID: <Pine.NEB.4.64.0705231513070.10660@panix2.panix.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>
This is a practical question related to application/foo+xml media types. I recognize that this is not a programming forum; I am posting here anyway because I think that this group will be keenly aware of the problem and interested in a solution. IE will only allow cross-domain requests for the text/xml or application/xml types. It does not support application/foo+xml. Does anyone know of a workaround which would allow me to avoid having to publish resources with the wrong (application/xml) type? If I do have to publish with the wrong type, does anyone know of a method which would allow me to minimize the damage? This is important because it is a limiting factor for all XML-based formats. Thank you. -Lucas Gonze
- practical question Lucas Gonze