[Koha-bugs] [Bug 16579] Use separate memcached namespace for caching koha-conf.xml

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16579

Srdjan Jankovic <srdjan at catalyst.net.nz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |srdjan at catalyst.net.nz

--- Comment #25 from Srdjan Jankovic <srdjan at catalyst.net.nz> ---
(In reply to Jacek Ablewicz from comment #24)
> By the look of it, in regards of cache architectural changes, there will be
> some overlap with Bug 15562, which in parts does somehow similar things with
> the cache (and a lot of other interesting things as well, but it's huge and
> I don't really understand ~half of it). Are there any chances of coordinated
> effort of some sort, so they both don't clash too badly with each other?

That's terrible. Next time I rebase I'll try to make it more readable.
Apologies.

Changes presented here are almost identical to the changes 15562, except that
they are a bit better:
* I fell short of introducing Koha::Config which I should have (I chickened
out)
* Koha::Caches - maybe we need to mandate the namespace when instantiating
Koha::Cache in order for this to be more robust?

At any rate, I did my patch in order to make plack multi-host going, and to be
brutally honest I was expecting things in the Cache/Context land to change a
lot by the time my patch gets some love. The issue is very complex, so it is
probably good to have independent efforts at early stages. Helps with
discovering unforeseen situations.

One thing that might be worth thinking about is that the very same problem
exists with the database connections. So maybe some über class, Koha::Storage
or something that would have a slot for everything we use, and then
Koha::Storages collection keyed by the namespace?

-- 
You are receiving this mail because:
You are watching all bug changes.