<div dir="ltr"><div><div><div><div><div><div><div>Is there an estimate of how much work/time it would take to refactor the library to slowly satisfy those three points?<br></div>Also, do we already have clear ideas on where we want to get? While the three points are clear from a general point of view, what does each of those points really mean? Which parts have you identified as "not easy to understand", what architecture you have in mind when speaking about "modern Python-based web applications"? IIRC you suggested Pecan as a reference.<br><br></div>About point #2, I think it could be the "easiest" to fix, even thou not so elegantly at first, but I only see one bug report currently open about it (<a href="https://bugs.launchpad.net/wsme/+bug/1532704">https://bugs.launchpad.net/wsme/+bug/1532704</a>). The first step here would be to check the most common return codes used in APIs and see if WSME supports them or not... (*)<br><br></div>IMHO, if we are trying to fix it, the first step should be to have a clear plan as to encourage volunteer contributions, even thou there are not many of those.<br><br></div>That's my 2 cents!<br><br></div>Cheers,<br></div>Stéphane<br><br></div>(*) I remember that a change I did to correct an HTTP status code returned from WSME had an impact in the OpenStack projects using it. So before releasing a version with the correct status codes we have to remember to tell others to check their code to ensure it works with the correct status codes.<br><div><div><div><div><br></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 8, 2016 at 12:25 PM, Chris Dent <span dir="ltr"><<a href="mailto:cdent+os@anticdent.org" target="_blank">cdent+os@anticdent.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Last summer Lucas Gomes and I were press ganged into becoming core on<br>
WSME. Since then we've piecemeal been verifying bug fixes and generally<br>
trying to keep things moving. However, from the beginning we both agreed<br>
that WSME is _not_ a web framework that we should be encouraging. Though<br>
it looks like it started with very good intentions, it never really<br>
reached a state where any of the following are true:<br>
<br>
* The WSME code is easy to understand and maintain.<br>
* WSME provides correct handling of HTTP (notably response status<br>
and headers).<br>
* WSME has an architecture that is suitable for creating modern<br>
Python-based web applications.<br>
<br>
Last summer we naively suggested that projects that are using it move to<br>
using something else. That suggestion did not take into account the<br>
realities of OpenStack.<br>
<br>
So we need to come up with a new plan. Lucas and I can continue to<br>
merge bug fixes as people provide them (and we become aware of them) and<br>
we can continue to hassle Doug Hellman to make a release when one is<br>
necessary but this does little to address the three gaps above nor the<br>
continued use of the framework in existing projects.<br>
<br>
Ideas?<br>
<br>
Thanks.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Chris Dent (╯°□°)╯︵┻━┻ <a href="http://anticdent.org/" rel="noreferrer" target="_blank">http://anticdent.org/</a><br>
freenode: cdent tw: @anticdent</font></span><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Stéphane</div>
</div>