On Mon, 20 Dec 2010 09:38:21 -0200 Raphael Kubo da Costa <k...@profusion.mobi> said:
> > You're not supposed to. If you're doing http, you should explicitly know > > what request you're doing so url_send is not that good a function for this. > > > > You should have url_get, url_post, etc... *or* url_send should allow > > specifying the method. This would break API, though, so a middle term > > option would be to have explicit functions for that. > > OK, so we all agree that currently there's no way to use > ecore_con_url_send() to send a GET, a POST and a zero-length POST with > its current arguments. > > Can we deprecate ecore_con_url_send() and implement separate functions > for sending each method during the API freeze? yes we can. what we have here is an api bug. this is our last opportunity to "fix" such things or be stuck with them for years. probably should deprecate send and document it as a "it will guess if it should post or get" and have a post and get call added. it's important we kill such bugs now while we can (if possible in an elegant way). -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
