[wp-trac] [WordPress Trac] #28205: XMLRPC should probably expose Sideloading of images for shared hosts.
WordPress Trac
noreply at wordpress.org
Sun May 11 00:40:20 UTC 2014
#28205: XMLRPC should probably expose Sideloading of images for shared hosts.
-----------------------------+------------------------------
Reporter: georgestephanis | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: XML-RPC | Version: trunk
Severity: normal | Resolution:
Keywords: has-patch | Focuses:
-----------------------------+------------------------------
Comment (by redsweater):
I love the idea of working around the problem of WordPress's API falling
over easily on large media uploads. But I wonder if the better solution
would be to provide some mechanism through which clients could POST raw
binary data, akin to what happens when a user uploads media through the
wp-admin interface.
I know that uploading binary data is not possible in the pure XMLRPC
interface, but some kind of well-defined mechanism for POSTing binary
seems like a better long-term solution than relying upon uploading the
data to a separate location only to be "sideloaded" into WordPress.
What if there were a WordPress XMLRPC API that vended a binary POST URL
for more efficient uploads? Something like "wp.uploadBinaryFile" which
could yield a one-time URL suitable for POST-ing the desired binary data.
The URL could be pre-configured with some kind of session data that
assured its security and also connected it to the provisional file being
uploaded.
From my perspective it would be great to be able to tell WordPress, via
the XMLRPC API, that I have a file to upload, and here's all the metadata
about it (typical arguments to wp.uploadFile), but the data itself will be
coming in a subsequent POST to a specific URL.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/28205#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list