The Salesforce1 Platform (comprising Force.com, its REST API and much more) is anything but static, however, and ForceTK has just undergone a minor refit to bring it up to date. Let’s take a look at three changes in the current version.
/services/data) is exposed on the Visualforce servers, so the proxy is not required. The library will automatically call the REST API directly in this case. Note that Apex REST methods (
/services/apexrest) still require the proxy.
One final addition is the ability to insert and update Blob data via multipart messages – a REST API feature currently available through a pilot program. It is possible to insert or update blob data using a non-multipart message (by passing base64-encoded data in a JSON or XML-encoded message), but if you do, you are limited to 50 MB of text data or 37.5 MB of base64–encoded data. Using multipart messages, you can upload files of any type with a size of up to 500 MB. The new
updateBlob functions allow creation of
ContentVersion records and creation and update of
Document records. Here’s a minimal example that shows how it works:
If you’re using ForceTK, grab the new version and let me know what you think in the comments.