On 17/03/10 11:33 -0500, Gustavo Andrés Angulo wrote:
> Hi, when using HTTP authentication on every request the user and password
> are sent in the HTTP protocol in the section "credentials", I think this
> is wrong way, for to use HTTP authentication protocol I use HTTP + SSL (HTTPS)
> and if I
Hi, when using HTTP authentication on every request the user and password
are sent in the HTTP protocol in the section "credentials", I think this
is wrong way, for to use HTTP authentication protocol I use HTTP + SSL (HTTPS)
and if I want use HTTP the best way is to use a token something like
h
On 17/03/10 09:15 -0700, Ian Wilson wrote:
> I don't know much about this, but I thought repeating sending the
> username and password was frowned upon. Why is this a better approach
> than the session/login approach?
It is a standard method and later we could implement authentication for HTTP
1.
I don't know much about this, but I thought repeating sending the
username and password was frowned upon. Why is this a better approach
than the session/login approach?
On Wed, Mar 17, 2010 at 8:17 AM, Cédric Krier wrote:
> Hi,
>
> I propose to change the authentication mechanism used in XML-RPC
Hi,
I propose to change the authentication mechanism used in XML-RPC protocols.
Currently, it requires to call "login" function to retreive a user id and a
sesssion and pass this parameters at each function call.
My suggestion is to use the standard authentication of HTTP (first the Basic)
so the
Hi,
I propose to clean up the on_change functions signature.
Currently, it is like this:
def on_change_xxx(self, cursor, user, ids, vals, context=None):
pass
But as on_change could happen on non saved records, the ids list is not
usable and must never be used because the data from the databa
Please review this at http://codereview.appspot.com/612041/show
Affected files:
M trytond/model/model.py
Index: trytond/model/model.py
===
--- a/trytond/model/model.py
+++ b/trytond/model/model.py
@@ -113,6 +113,24 @@
