Memcached support in packages
Hi, i want to add out-of-the-box support for memcached for packages. There are two possible approaches to this: - As a required or suggested dependency that enables it globally if present - As an optional enable/disable per instance service. I'd like to hear what you devs see as the best approach with pros and cons. Regards To+
Hi, On Tue, May 28, 2013 at 7:22 AM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
- As a required or suggested dependency that enables it globally if present
At the very least, I think it should be a suggested dependency that is enabled globally.
- As an optional enable/disable per instance service.
Personally, I wouldn't need to be able to manage it per-instance, outside of debug situations. That raises a usage question: when would somebody choose to enable memcached for some instances but not all? Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
Tomas Cohen Arazi schreef op di 28-05-2013 om 11:22 [-0300]:
- As a required or suggested dependency that enables it globally if present - As an optional enable/disable per instance service.
I have no real problem with it being on by default, if someone really wants to toggle it they can edit koha-conf.xml anyway. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
At 10:19 AM 5/29/2013 +1200, Robin Sheat wrote:
Tomas Cohen Arazi schreef op di 28-05-2013 om 11:22 [-0300]:
- As a required or suggested dependency that enables it globally if present - As an optional enable/disable per instance service.
I have no real problem with it being on by default, if someone really wants to toggle it they can edit koha-conf.xml anyway.
Isn't this really an o/s question? If it isn't installed and enabled by Debian, RH, CentOs, Ubuntu, whatever, by default, why should an open-source install such as Koha usurp the o/s? Yes, it might be a good idea to *suggest* it if the o/s doesn't have it. Can Koha give some performance statistics? Can Koha be fairly certain that nothing else is compromised (and I'm pretty certain that nothing 'bad' will happen.) If not (and respectfully to you Robin), isn't it a wee bit arrogant to install it and then say "you can edit koha-conf.xml" and turn it off? I have used it regularly for couple of years now, no problems, but no proof of functional gain (or loss), I just take it for granted -- but have wondered why the various o/s's don't include it automatically. YMMV Best - Paul
Paul schreef op di 28-05-2013 om 19:48 [-0400]:
Isn't this really an o/s question? If it isn't installed and enabled by Debian, RH, CentOs, Ubuntu, whatever, by default, why should an open-source install such as Koha usurp the o/s?
We're specifically talking about the packages here, so RH, CentOs, etc don't count. Part of the goal of them is to provide an easy best-practice configuration, so having a recommendation/requirement of memcache is totally within the bounds of this.
Can Koha give some performance statistics? Can Koha be fairly certain that nothing else is compromised (and I'm pretty certain that nothing 'bad' will happen.) If not (and respectfully to you Robin), isn't it a wee bit arrogant to install it and then say "you can edit koha-conf.xml" and turn it off?
We have a testing cycle for this. If it's discovered that it causes problems in some set of circumstances, we can either fix that case, revisit our plan to include it, or whatever is appropriate.
I just take it for granted -- but have wondered why the various o/s's don't include it automatically.
That wouldn't make sense. Applications have to be made to work with it. There's no point running it if nothing you're using can use it. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
On 2013-05-29, at 10:19 AM, Robin Sheat wrote:
Tomas Cohen Arazi schreef op di 28-05-2013 om 11:22 [-0300]:
- As a required or suggested dependency that enables it globally if present - As an optional enable/disable per instance service.
I have no real problem with it being on by default, if someone really wants to toggle it they can edit koha-conf.xml anyway.
-- Robin Sheat
agreed +1 for global, on by default
participants (5)
-
Galen Charlton -
Mason James -
Paul -
Robin Sheat -
Tomas Cohen Arazi