Use generic queries instead of specialized index queries. This is a step
towards the publisher app, because its client will have to use generic
queries.
Context: http://camlistore.org/issue/365
Change-Id: I2781a345e024174e3bea8511b6cdc6f342d5a7c1
Didn't find anything, but is useful to keep in, to maybe find bugs in the future
for other storage types.
Change-Id: If0fd37e03578de233be8da95ca45623c5f12156b
Depending on timing, could lead to ListMissingDestinationBlobs getting out
of sync and causing a lot of blobs to be replicated that were fine and already
on the server.
Change-Id: I3710e59088f1fe4e526f8f11bc9d1837a727e512
StreamingFetcher is now just Fetcher, and its FetchStreaming is now
just Fetch.
SeekFetcher is gone. Blobs are max 16 MB anyway, so we can slurp to
memory when needed. The main thing that cared about SeekFetcher
was the GET handler, ServeBlobref, because http.ServeContent needed
one for range requests. That's rewritten in an earlier commit, using
the FakeSeeker from another earlier commit.
Lot of code got simpler as a result.
Change-Id: Ib819413e48a8f9b8d97f596d0fbf771dab211f11
Currently controlled by an environment variable, but will become
a config option + on-demand button in UI in later commits.
Change-Id: I25fa878c9b30cdd713e2859585210eb722092f7b
Fix deadlock, much better status page, show per-blob status & errors,
clear errors when they've resolved themselves, fix known data race.
Change-Id: I968de0de4f308ff0a410adceb181a0712800d401
Creates new page @ /ui/mobile.html for generating a QR code that
embeds configuration data for setting up mobile clients.
Imports code.google.com/p/rsc/{gf256,qr} version:
parent: 149:a3cbaf2339c4 tip
This addresses the server and web components of
https://camlistore.org/issue/372
Change-Id: If9239dd138707080afd7dedb5770d04893cbf0ba
Not just in blob.SizedRef, but in blobserver.Fetch and
blobserver.FetchStreaming, too.
Blobs have a max size of 10-32 MB anyway, and the index.Corpus is now using
uint32 to save memory.
Change-Id: I1172445c2f9463fdaee55bfe0f1218d44be4aa53
Bytes read/writen per pack file, as well as per configured diskpacked
configuration are now available as expvars.
Also add reader stat helpers to pkg/types and updated the original
user in server/image.go
Change-Id: Ifc9d76c57aab329d4b947e9a4ef9eac008bc608d
Move from one pool for all thumbnail resizing to per-ImageHandler
instace.
Uses the value of "maxResizeBytes" if specified in the "handlerArgs"
section of a "publish" or "ui" handler's low-level config.
If we end up wanting to share pools, i.e. if all published
handlers should share a pool, we'll need to do a bit more work.
Implements suggestion from https://camlistore.org/r/1803 review.
Further improves on https://camlistore.org/issue/316.
Change-Id: Ia93fad119b546064173ac3e2c7f0ab8509744628
The RAM limit is based on the expected amount of allocations not the
measured allocation.
Issue https://camlistore.org/issue/316
Change-Id: I3ccff6ddf880f3f9a90f6c27f15f9662fad02712
The detail view now loads with only two HTTP requests: one for the
piggy, and one for the big image. No other resources are loaded,
even the blob descriptions, because they are cached by SearchSession,
which is shared between the search ui and the detail ui.
Likewise, when you go back to the search results page, no additional
requests are done.
Also:
- When you press back on detail page, scroll position is now usually
restored (if you refresh between index and detail, it still won't
restore).
- Detail page live updates! It came for free with using SearchSession.
Change-Id: I58ada7bdd30afc2644860fbda6167fc5ce865b0d
In camlistored, only react.min.js is served. In devcam all files in
the read directory are served.
Change-Id: I0cb8a4c328e550b5303edef4be7571d39d123340
Fixes warning 'Resource interpreted as Image but transferred with MIME
type text/xml:' on Chrome, and more importantly returns the previously
missing icons to my camlistore instances. Everyone else must be
hitting cache, or something is weird with my setup. I see missing
icons on Safari / Chome on Mac, and Firefox / Chrome on Linux.
Change-Id: I4809d8c7948a49fe80fdf1a97ac98b2161ba0307
And quiet noisy logging on normal write failures.
We can now stress test the thumbnail generation by setting
CAMLI_DISABLE_THUMB_CACHE=1 which will make all the thumbnails in the
browsers be unique, and not write them to cache on the server.
Then, when we're happy with the thumbnails, we just increment the
thumbnailVersion string and that busts all the browser- and
server-side caches.
Change-Id: I3cda8e85ab8b1b0b2c9113f6dff613dfbf736028
mpl