Am 28.03.2009 um 00:05 schrieb Michael Nordman:
The behavior you describe is not the the intended behavior. You
certainly
should be able to store.getAsBlob(url) any resource that resides
within
that resource store. What does store.isCaptured(url) have to say
about the
resource you are interested in?
Also you mention something about manifest files? ManagedResourceStores
does not provide a getAsBlob() method at all... so this bit about
manifest files
in your question confuses me?
Here's the full scenario: I have a form where the user can capture
data (text data into database and binary files into a ResourceStore,
with references in the database). This form is accessible via an url
which has an entry in the manifest file, so he can gather data when
he's not online.
Later, when he is logged in and accesses an url where he can upload
the gathered data (this url is not in the manifest file and so not
accessible offline), I can read the local database and upload all the
data, but not get locally stored files from the ResourceStore (not the
ManagedResourceStore). Even if I set "myresourcestore.enabled=true",
Gears does not serve a binary files from the local cache: I get the
message "Failed to load blob". When I check store.isCaptured(), I get
"false" on this page. When I check it at a url which is accessible
offline, loading the blob succeeds.
My urls look like this:
/capture/offline (-> has an entry in the manifest file, works fine.
Accessing blobs works.)
/sync (-> not available online, only for logged-in users.
Shall start the upload process. Accessing blob fails.)
I could image that this is not possible by design since the url where
I want to start the upload process is not cached. If this is the case,
how can I upload the binary data correctly from a script running under
a not-cached-url?
Hope the problem is clearer now.
