| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the initial refactoring to improve how we deal with the storage.
It does a couple of things:
* Rename Sink::Storage to Sink::Storage::DataStore to free up the
Sink::Storage namespace
* Introduce a Sink::ResourceContext to have a single object that can be
passed around containing everything that is necessary to operate on a
resource. This is a lot better than the multiple separate parameters
that we used to pass around all over the place, while still allowing
for dependency injection for tests.
* Tie storage access together using the new EntityStore that directly
works with ApplicationDomainTypes. This gives us a central place where
main storage, indexes and buffer adaptors are tied together, which
will also give us a place to implement external indexes, such as a
fulltextindex using xapian.
* Use ApplicationDomainTypes as the default way to pass around entities.
Instead of using various ways to pass around entities (buffers,
buffer adaptors, ApplicationDomainTypes), only use a single way.
The old approach was confusing, and was only done as:
* optimization; really shouldn't be necessary and otherwise I'm sure
we can find better ways to optimize ApplicationDomainType itself.
* a way to account for entities that have multiple buffers, a concept
that I no longer deem relevant.
While this commit does the bulk of the work to get there, the following
commits will refactor more stuff to get things back to normal.
|
| |
|
|
| |
(except for documentation).
|
| | |
|
| |
|
|
| |
Mails in inbox!
|
| |
|
|
| |
Adding new types definitely needs to become easier.
|
| | |
|
| |
|
|
| |
A default implementation is now nothing but an empty shell.
|
| |
|
|
| |
With equality filter on arbitrary properties as a bonus.
|
| | |
|
| | |
|
| |
|
|
|
| |
There is always exactly one default buffer that we can centralize
in TypeImplementation.
|
| | |
|
| | |
|
| |
|
|
| |
First prepare the result set, then retrieve it.
|
| | |
|
| | |
|
| |
|
|
| |
The dummy resource could now implement incremental queries.
|
| | |
|
| |
|
