[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: atompub-multipart-01: browser implementation
- To: "Bill de hOra" <bill@xxxxxxxxxx>
- Subject: Re: atompub-multipart-01: browser implementation
- From: "Joe Gregorio" <joe@xxxxxxxxxxxxxx>
- Date: Thu, 19 Jun 2008 10:58:08 -0400
- Cc: "Atom Protocol" <atom-protocol@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=dPM9ivcm1KR7oX/3zzMW/wLya9yKXVbTnatFOyXdHQY=; b=F+GbRGNNilbpyx6sFqrRPLPD58SJdQRHO+Lz1Rgk0jbgtu9AlSiZnwN6Qdt2N13dlP +fyQ87P6H06qXJlHZVhUrm4hTA6ZnspJylRIjizGBjb80xYaP9CIK2ddO28aQJKtjrRs Tl7hIS1BGqOlLJ/axt+bgHW7bAHT6nGves9iY=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=q8yw6xZTB/cfzyLCGwBl8yKButqyLqnuxXQv1D4EOaCdmC/5hVr2FdrSEIqArNGVLS BMpu2p8HnjXmXWxLBOsqwPRbm6GlA7xkOe45Jq0yp41SyW2d6Vt29fiD/nqzt4MBUgP2 IIkqqqMA5suNV53+NfYS/S2hZkYv125rCBhns=
- In-reply-to: <485A5783.3010004@xxxxxxxxxx>
- List-archive: <http://www.imc.org/atom-protocol/mail-archive/>
- List-id: <atom-protocol.imc.org>
- List-unsubscribe: <mailto:atom-protocol-request@imc.org?body=unsubscribe>
- References: <485A5783.3010004@xxxxxxxxxx>
- Sender: owner-atom-protocol@xxxxxxxxxxxx
On Thu, Jun 19, 2008 at 8:56 AM, Bill de hOra <bill@xxxxxxxxxx> wrote:
>
> http://www.ietf.org/internet-drafts/draft-gregorio-atompub-multipart-01.txt
>
> When doing multipart, browsers/AJAX can't load files from the file system.
> As a result XHR objects generally can't submit non-text content. The
> standard (only?) workaround for this is a hack that allows a form post to be
> sent via a hidden iframe. At that point there's no way to set headers and
> the client is limited to application/x-www-form-urlencoded or
> multipart/form-data (due to HTML forms).
Doesn't this mean that the same is true for posting media files to an
AtomPub collection
in a browser?
> Short version: I think this draft can't be implemented in a browser [1].
True, but has working in a browser ever been a self-imposed constraint
of AtomPub?
-joe
--
Joe Gregorio http://bitworking.org