organizing resource events

this is specifically for the resource cache graph, so the script doesn't
need to ignore the ResourceNotFound event. Convenience! lol
smarter timers

cancel keys are maintained internally and associated to opaque strings. code has been refactored. the API is more or less what the browsers have established, except for timing around setInterval, which for now takes execution time into consideration before scheduling the next interval. the test is also much improved.
not accessing a field directly anymore
updates to the resource cache stuff.  it's working!

need to figure out a way to get the output into the core? i don't know
yet, exactly, but it's pretty cool right now for real!
minor cleanup

just straightened out a bit while refreshing my memory about what i was
doing here.  i think i may be revisiting this shortly, the routing
concepts are becoming clearer in my head
renaming the messaging package to i18n

time to expose this via API, and flesh out the notion of configuring Locales for the server
further i18n work

adding a configuration.  also renamed the module
simplify the reading of accept-lang headers

java 7 added a nice method for doing what i was doing by hand.  hah
minor cleanup
moved the resource name into the base class

next up, URIs, which will come from the creator

then making the ServableResource, which will have a mimeType and a
serverPath and maybe other interesting stuff too, and will interact with
the routing system, ultimately replacing the notion of the Servable,
which let's face it, is crap and needs to diediedie
introducing the ServableResource

making the notion of resources that can be served into something a little more generic. specifically, i want to kill off the "servable" structure, and just make the parts of the system the can be served understand how to serve themselves.  or at least declare their own classes for such a job.  as it is right now, it's a little too messy and not amenable to what i am aiming for.

this at least gets rid of the notion of trying to declare a server URI for things that won't get served. next step is to do the public/private split, i think
making servability decisions more generic

working toward killing off that whole servable structure. SO CLOSE
continuing refactorings in the Servable structure

thinking through how to kill all of this off
moving alive method to the Resource interface

it's reasonable there.
simplification of an API

removing a redundant parameter
introduction of an API for loading MessageResource contents in script

it feels necessary.  but there are some complications because of dynamic
typing.  but here is cut #1
minimal API for i18n messages

this needs some error handling of some sort but it's here for now