already created resource manager. Due to the way the Handler stuff is set
up, only the first resource manager ever created in a JVM will be wired up
to handle resource: URLs and thus we have to be careful to only ever
create one resource manager.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3499 542714f4-19e9-0310-aa3c-eee0fc999fb1
implementations do a fucking DNS lookup on the host of the URL. The degree
to which that violates expectations about the "expense" of calling
hashCode() is so astronomical as to be unexpressible without complicated
metaphor.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3421 542714f4-19e9-0310-aa3c-eee0fc999fb1
load resources to load from the default sets.
(A normal url would be "resource://<set>/<path>", one using the default set
would be "resource:///<path>". Goofy.)
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3396 542714f4-19e9-0310-aa3c-eee0fc999fb1
loads, but the sound manager wants to load things directly from the
classpath, so we need to allow it to use the classpath that the resource
manager was configured with to ensure that it did the right thing.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3379 542714f4-19e9-0310-aa3c-eee0fc999fb1
Java's magical security system to do the right thing (or so I think).
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3274 542714f4-19e9-0310-aa3c-eee0fc999fb1
it's unlikely that the rabbit hole will surprise us with further depth.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3269 542714f4-19e9-0310-aa3c-eee0fc999fb1
out Getdown's "verified" marker file so that Getdown will recompute the
jar file's MD5 hash and then wipe it out and redownload it only if it is
actually corrupted.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3146 542714f4-19e9-0310-aa3c-eee0fc999fb1
Added extra special magic to allow the resource: URLs to extract a tile
from an image that is actually made up of a bunch of smaller images. It's
so money.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3083 542714f4-19e9-0310-aa3c-eee0fc999fb1
ready prior to even waiting for it. Handle that case.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3061 542714f4-19e9-0310-aa3c-eee0fc999fb1
handle downloading of resources, it simply manages them in situ. Getdown
is now responsible for all the downloading.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3060 542714f4-19e9-0310-aa3c-eee0fc999fb1
into a properties object so that we can log the text if Java chokes.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3034 542714f4-19e9-0310-aa3c-eee0fc999fb1
about handling resources that didn't provide a content length.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3030 542714f4-19e9-0310-aa3c-eee0fc999fb1
content-length header even though the servlet container is providing one.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3029 542714f4-19e9-0310-aa3c-eee0fc999fb1
more discipline when handling names in our code base. Any user entered
name should find its way into a Name object as soon as it comes out of a
text field or whatnot, and stay that way until it makes its way into a
text field or into a database record (for which String objects are vastly
simpler because of JORA magic).
Dear God, let me never again make a change this large for the rest of my
mortal life.
Unfortunately, this means we have to keep an eye out for funny business
pretty much everywhere. However, since we will absolutely want to test
market stalls and so forth on Azure, we'll have an opportunity to iron out
any funny business that might fall under the radar during our internal
testing.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2980 542714f4-19e9-0310-aa3c-eee0fc999fb1
expression because Windows \s in paths booch the regex code to the high
heavens.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2922 542714f4-19e9-0310-aa3c-eee0fc999fb1
previous releases that sometimes cannot be deleted because of the
mysterious "no you can't delete a file that you created" Windows bug.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2915 542714f4-19e9-0310-aa3c-eee0fc999fb1
don't leave any unversioned bundles lying around after a conversion.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2847 542714f4-19e9-0310-aa3c-eee0fc999fb1
named according to its version number so that when we patch an old version
to create a new version, we don't have to do any renaming, we just create
the new version directly and hopefully avoid this bullshit problem on
Windows where we're unable to rename a goddamned file.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2846 542714f4-19e9-0310-aa3c-eee0fc999fb1
programmatically or it will be assumed to be the same as the normal
resource URL.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2774 542714f4-19e9-0310-aa3c-eee0fc999fb1
around in there for other reasons. We also avoid looking up the entry in
the jar file every time it is requested.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2766 542714f4-19e9-0310-aa3c-eee0fc999fb1
successfully unpacked its jar file so that we can report bundle download
borkage and retry in the face of potentially transient fuckolas.
git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@2764 542714f4-19e9-0310-aa3c-eee0fc999fb1
Michael Bayne