Le 12/12/2011 17:24, Ian Walls a écrit :
> My difficulty with this patch is that it sets precedent for implementing
> both commandline and staff client interfaces for a single script. Up
> until now, that's not be the case (as far as my research has shown;
> counter-examples welcome). I just think we need, for consistency sake,
> to either make this the standard practice, or require separate cronjobs.
>
> So, I don't have any issue with the feature, but the potential shift in
> coding practices that the patch represents. Is the rest of the Koha
> developer community comfortable with having dual-purpose scripts like
> this? Are there are any best practices that can be cited for or against
> such practice?
As I said already (on the ML iirc), there are only a very few cases
where this should be relevant. So I think it's not worth spending too
much time deciding if it should be a rule or not
--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08
_______________________________________________
Koha-devel mailing list
[email protected]
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
