[storm] Profiling project: terminology

[Ian Booth]

> 
> For now I went with "fetch," which is an established term for a similar
> action in processor architecture.  It also combines naturally into
> "prefetching," which is a special kind of fetching.
> 
> Does anybody have any suggestions, opinions, solutions?  It may seem
> strange that I attach so much importance to one verb, but it pops up in
> all sorts of ways: fetch contexts, fetch profiles, fetch statistics,
> fetch callback functions, and so on.
> 

I think "fetch" is ok. Perhaps showing my Java/Hibernate heritage, I
also like "hydrate" and "dehydrate" (for going the other way). These
terms are also used by other ORM solutions. The thing I like is that
they are not overloaded uses of verbs which may have multiple meanings
in other contexts like "cache" etc. But then again, their meaning may
not be intuitive to people without previous ORM experience.