[prev in list] [next in list] [prev in thread] [next in thread]
List: openmrs-dev
Subject: Re: RESTWS-251, 365: Subclass handlers
From: Darius Jazayeri <darius () openmrs ! org>
Date: 2013-02-28 21:15:04
Message-ID: CAA-nHnfCWA-fES9_tbbKpgq_B4jPHw+p9e_cFON_2W1+mZJkGQ () mail ! gmail ! com
[Download RAW message or body]
Hi Roger,
To expound on Rafal's meta point: our philosophy is to be agile, and to try
to make more frequent, smaller releases, where we can add functionality in
an incremental way. It's nearly always better to release something early,
so people can poke at it and suggest fixes. (And I don't think this is one
of the 1% of cases where we want to delay a release.)
It's the nature of the work that our resources are limited, and we can't do
everything we'd ideally like to. The agile approach is actually really
helpful here, and it tells us to release what we've been able to build, and
let people use it and give us feedback. Not releasing the code, once
resources are focused elsewhere, just lengthens our feedback cycle.
(I agree that these tickets are important--I've only said that they are
"insufficiently important" for the *current sprint*, which is actually
over!)
-Darius
On Thu, Feb 28, 2013 at 10:17 AM, Friedman, Roger (CDC/CGH/DGHA) (CTR) <
rdf4@cdc.gov> wrote:
> These capabilities seem really basic, it's not great if someone starts
> to write a subclass-based module and discovers that "at any point" has not
> yet arrived (that's how we got into subclass handlers in the first place).
> ****
>
> ** **
>
> I'm particularly worried about the t= searches/gets. If you assure me
> that they will work with the same code as before, it's just that you can't
> select which subclass handler to use based on OpenMRS version, I'd be a lot
> happier.****
>
> ** **
>
> *From:* rafal.korytkowski@gmail.com [mailto:rafal.korytkowski@gmail.com] *On
> Behalf Of *Rafal Korytkowski
> *Sent:* Thursday, February 28, 2013 12:40 PM
> *To:* Developers List
> *Subject:* Re: RESTWS-251, 365: Subclass handlers****
>
> ** **
>
> It's definitely worthwhile to do these tickets otherwise they would have
> been closed as won't fix ;)****
>
> ** **
>
> I don't think they block the 2.0 release. A better support for subclass
> handlers is not backwards incompatible in any way and can be added to any
> release at any point.****
>
>
> ****
>
>
> -Rafał****
>
> ** **
>
> On 28 February 2013 18:11, Friedman, Roger (CDC/CGH/DGHA) (CTR) <
> rdf4@cdc.gov> wrote:****
>
> https://tickets.openmrs.org/browse/RESTWS-251 Resource-per-class-hierarchy
> model needs to also support subresources<https://tickets.openmrs.org/browse/RESTWS-251>
> ****
>
> https://tickets.openmrs.org/browse/RESTWS-365 Load subclass handlers
> based on OpenMRS version <https://tickets.openmrs.org/browse/RESTWS-365>**
> **
>
> Support for subtype-based searches****
>
> ****
>
> These issues represent basic features of the REST API that have not been
> implemented for subclass handlers in the belief that subclasses are
> insufficiently important or used to making finishing them worthwhile.
> However, subclasses are key to our ordering work and have many applications
> such as billing or drug trials or lab. People may not have understood the
> implementation of subclasses in RESTWS up to now due to lack of
> documentation. My feeling is that they are "musts" before the next version
> of RESTWS should be released. ****
>
> --
> OpenMRS Developers: http://go.openmrs.org/dev
> Post: dev@openmrs.org
> Unsubscribe: dev+unsubscribe@openmrs.org
> Manage your OpenMRS subscriptions at https://id.openmrs.org/
>
> ****
>
> ** **
>
> --
> OpenMRS Developers: http://go.openmrs.org/dev
> Post: dev@openmrs.org
> Unsubscribe: dev+unsubscribe@openmrs.org
> Manage your OpenMRS subscriptions at https://id.openmrs.org/
>
> ****
>
> --
> OpenMRS Developers: http://go.openmrs.org/dev
> Post: dev@openmrs.org
> Unsubscribe: dev+unsubscribe@openmrs.org
> Manage your OpenMRS subscriptions at https://id.openmrs.org/
>
>
>
--
OpenMRS Developers: http://go.openmrs.org/dev
Post: dev@openmrs.org
Unsubscribe: dev+unsubscribe@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/
[Attachment #3 (text/html)]
<div dir="ltr">Hi Roger,<div><br></div><div>To expound on Rafal's meta point: our \
philosophy is to be agile, and to try to make more frequent, smaller releases, where \
we can add functionality in an incremental way. It's nearly always better to \
release something early, so people can poke at it and suggest fixes. (And I don't \
think this is one of the 1% of cases where we want to delay a release.)</div>
<div><br></div><div style>It's the nature of the work that our resources are \
limited, and we can't do everything we'd ideally like to. The agile approach \
is actually really helpful here, and it tells us to release what we've been able \
to build, and let people use it and give us feedback. Not releasing the code, once \
resources are focused elsewhere, just lengthens our feedback cycle.</div>
<div style><br></div><div style>(I agree that these tickets are important--I've \
only said that they are "insufficiently important" for the <i>current \
sprint</i>, which is actually over!)</div><div> <br></div><div>-Darius</div><div \
class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 28, 2013 at 10:17 \
AM, Friedman, Roger (CDC/CGH/DGHA) (CTR) <span dir="ltr"><<a \
href="mailto:rdf4@cdc.gov" target="_blank">rdf4@cdc.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">These \
capabilities seem really basic, it's not great if someone starts to write a \
subclass-based module and discovers that "at any point" has not yet arrived \
(that's how we got into subclass handlers in the first place). \
<u></u><u></u></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> \
<u></u></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I'm \
particularly worried about the t= searches/gets. If you assure me that they will \
work with the same code as before, it's just that you can't select which \
subclass handler to use based on OpenMRS version, I'd be a lot \
happier.<u></u><u></u></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> \
<u></u></span></p> <p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span \
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a \
href="mailto:rafal.korytkowski@gmail.com" \
target="_blank">rafal.korytkowski@gmail.com</a> [mailto:<a \
href="mailto:rafal.korytkowski@gmail.com" \
target="_blank">rafal.korytkowski@gmail.com</a>] <b>On Behalf Of </b>Rafal \
Korytkowski<br> <b>Sent:</b> Thursday, February 28, 2013 12:40 PM<br>
<b>To:</b> Developers List<br>
<b>Subject:</b> Re: RESTWS-251, 365: Subclass \
handlers<u></u><u></u></span></p><div><div> <p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">It's definitely worthwhile to do these tickets otherwise \
they would have been closed as won't fix ;)<u></u><u></u></p> <div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I don't think they block the 2.0 release. A better support \
for subclass handlers is not backwards incompatible in any way and can be added to \
any release at any point.<u></u><u></u></p> </div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><br>
-Rafał<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On 28 February 2013 18:11, Friedman, Roger (CDC/CGH/DGHA) (CTR) \
<<a href="mailto:rdf4@cdc.gov" target="_blank">rdf4@cdc.gov</a>> \
wrote:<u></u><u></u></p> <div>
<div>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><a \
href="https://tickets.openmrs.org/browse/RESTWS-251" \
target="_blank">https://tickets.openmrs.org/browse/RESTWS-251</a> </span><span \
style="font-size:10.0pt;font-family:"Arial","sans-serif""><a \
href="https://tickets.openmrs.org/browse/RESTWS-251" \
target="_blank">Resource-per-class-hierarchy model needs to also support \
subresources</a></span><u></u><u></u></p>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><a \
href="https://tickets.openmrs.org/browse/RESTWS-365" \
target="_blank">https://tickets.openmrs.org/browse/RESTWS-365</a> </span><span \
style="font-size:10.0pt;font-family:"Arial","sans-serif""><a \
href="https://tickets.openmrs.org/browse/RESTWS-365" target="_blank">Load subclass \
handlers based on OpenMRS version</a></span><u></u><u></u></p>
<p class="MsoNormal"><span \
style="font-size:10.0pt;font-family:"Arial","sans-serif"">Support \
for subtype-based searches</span><u></u><u></u></p> <p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> \
</span><u></u><u></u></p> <p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">These \
issues represent basic features of the REST API that have not been implemented for \
subclass handlers in the belief that subclasses are insufficiently important or used \
to making finishing them worthwhile. However, subclasses are key to our ordering \
work and have many applications such as billing or drug trials or lab. People may \
not have understood the implementation of subclasses in RESTWS up to now due to lack \
of documentation. My feeling is that they are "musts" before the next \
version of RESTWS should be released. </span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><span><span style="color:#888888">-- </span></span><span \
style="color:#888888"><br> <span>OpenMRS Developers: <a \
href="http://go.openmrs.org/dev" target="_blank"> \
http://go.openmrs.org/dev</a></span><br> <span>Post: <a href="mailto:dev@openmrs.org" \
target="_blank">dev@openmrs.org</a></span><br> <span>Unsubscribe: <a \
href="mailto:dev%2Bunsubscribe@openmrs.org" target="_blank"> \
dev+unsubscribe@openmrs.org</a></span><br> <span>Manage your OpenMRS subscriptions at \
<a href="https://id.openmrs.org/" target="_blank"> \
https://id.openmrs.org/</a></span><br> <span> </span><br>
<span> </span></span><u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <br>
OpenMRS Developers: <a href="http://go.openmrs.org/dev" \
target="_blank">http://go.openmrs.org/dev</a><br>
Post: <a href="mailto:dev@openmrs.org" target="_blank">dev@openmrs.org</a><br>
Unsubscribe: <a href="mailto:dev+unsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a><br> Manage your OpenMRS subscriptions \
at <a href="https://id.openmrs.org/" target="_blank">https://id.openmrs.org/</a><br> \
<br> <u></u><u></u></p>
</div></div></div>
</div><div><div>
<p></p>
-- <br>
OpenMRS Developers: <a href="http://go.openmrs.org/dev" \
target="_blank">http://go.openmrs.org/dev</a><br>
Post: <a href="mailto:dev@openmrs.org" target="_blank">dev@openmrs.org</a><br>
Unsubscribe: <a href="mailto:dev%2Bunsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a><br> Manage your OpenMRS subscriptions \
at <a href="https://id.openmrs.org/" target="_blank">https://id.openmrs.org/</a><br> \
<br> <br>
</div></div></blockquote></div><br></div></div>
<p></p>
-- <br />
OpenMRS Developers: <a \
href="http://go.openmrs.org/dev">http://go.openmrs.org/dev</a><br />
Post: dev@openmrs.org<br />
Unsubscribe: dev+unsubscribe@openmrs.org<br />
Manage your OpenMRS subscriptions at <a \
href="https://id.openmrs.org/">https://id.openmrs.org/</a><br /> <br />
<br />
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic