WADL, WSDL 2.0 REST<br><br>[1] <a href="http://www.w3.org/Submission/wadl/">http://www.w3.org/Submission/wadl/</a><br><br>Async: cool and useful<br>gzip: def, probably the easiest upgrade<br><br><div class="gmail_quote">On Tue, Jun 22, 2010 at 6:00 PM, Daniel Rodriguez <span dir="ltr"><<a href="mailto:danjrod@gmail.com">danjrod@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Just like Joshua I think that some extra time can be given to get an important feature polished.<div>
<br></div><div>I am happily working with 0.3.9 and I think so far suds is covering the needs of most users (leaving apart those who are looking for things that suds can't provide like writing a service, for example)</div>
<div><br></div><div>As I opened a couple of tickets for enhancements (with patches included) I would like to know your view on such changes making it to 0.4</div><div><ul><li>Asynchrounous usage of suds (312)</li><li>Exception improvement by having a general SudsError and deriving all exceptions from there (310). I see someone opened 324 reporting some base "Exceptions" being launched which I can confirm</li>
<li>Transport with gzip support (311 and 318)</li></ul><div><br></div><div>Best regards</div><div><br></div><font color="#888888"><div>Daniel</div></font><div><div></div><div class="h5"><div><br></div><div class="gmail_quote">
On Fri, Jun 18, 2010 at 18:15, Joshua J. Kugler <span dir="ltr"><<a href="mailto:joshua@eeinternet.com" target="_blank">joshua@eeinternet.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">On Friday 18 June 2010, Jeff Ortel elucidated thus:<br>
<div>> The 0.4 release is mostly ready to go out but I'm not completely<br>
> happy with the 'plugins' API. I can either release as is with the<br>
> caveat that it /may/ change. Or, I can wait and get it the way I<br>
> want it first.<br>
<br>
</div>Since the plugin feature is going to be a "big deal," I would lean<br>
toward getting it right. You certainly want it to be well thought out,<br>
clean, and easy to use. Releasing a poorly implemented feature gives a<br>
project a bad reputation, and maybe worse: give the feature a bad<br>
reputation, which means it will be used less or not at all.<br>
<br>
We'll wait. I'd rather have a feature that works well than one I have<br>
to hack around to get it to do what I want.<br>
<br>
j<br>
<font color="#888888"><br>
--<br>
Joshua Kugler<br>
Part-Time System Admin/Programmer<br>
<a href="http://www.eeinternet.com" target="_blank">http://www.eeinternet.com</a><br>
PGP Key: <a href="http://pgp.mit.edu/" target="_blank">http://pgp.mit.edu/</a> ID 0x73B13B6A<br>
</font><div><div></div><div>_______________________________________________<br>
suds mailing list<br>
<a href="mailto:suds@lists.fedoraproject.org" target="_blank">suds@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/suds" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/suds</a><br>
</div></div></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
suds mailing list<br>
<a href="mailto:suds@lists.fedoraproject.org">suds@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/suds" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/suds</a><br></blockquote></div><br>