noosfero | Noosfero API (#500)

Aurélio A. Heckert gitlab at gitlab.com
Wed Mar 11 15:30:58 BRT 2015


New comment for Merge Request 500

https://gitlab.com/noosfero/noosfero/merge_requests/500#note_943385


Aurélio A. Heckert

I don't know this require inside a module could change a method for the entry application. Anyway, is it really a problem? It adds optional feature...

About the client in background, i believe that will be a big problem because the intention of the `location_to_georef` method is to be synchronous and be used in a stack of synchronous methods. What that really need is a cache. I will try memcache...

About the google issue, we do not give any other personal information. It is only an address. I don't get the point. Well, we can own the georef translation process with this proposal: http://noosfero.org/Development/ActionItem2970 Without this function we will not get the e-commercer api working as specified.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listas.softwarelivre.org/pipermail/noosfero-dev/attachments/20150311/7d41b138/attachment-0001.html>


More information about the Noosfero-dev mailing list