Your steps seem logical but, Problem is that the some clients are necessary in the browser, so there is no form to submit. Those clients needs a "fixed" end point to upload the data (or call a "fixed" end point that will return the upload url"
On Sep 7, 6:29 pm, timwhunt <timwh...@gmail.com> wrote: > I think I have this right, so hopefully to clarify: > > 1) You get the upload URL for an HTML form for your user to upload the > image. Part of forming that uploading URL is to identify the handler > code (e.g., Servlet in Java) > 2) Your handler code gets called by the Blobstore after the upload is > complete and that handler can work with the uploaded data and you'll > work with the the key for the blob > 3) Your handler sends a redirect command back to the user's browser > directing them to the page they need to go to for status/results. > That redirect URL generally includes a parameter identifying which > blob upload (it's key) you're dealing with. > 4) The user's browser is redirected to that page, where your code uses > the blobstore key (from the URL parameter) to process and in your case > return the OCR data. > > So from the client point of view, they submit a forum with a file > upload part, and they get redirected to the page that provides the > results. > > Someone please correct if necessary. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
