arsousa wrote: > > I had to make one little change in qcl source to put authentication works > for me. There are two possibilities of authentication , with user and > password other with session id. Both use the same rpc method > "authenticate", but the parameters are different. RPC4Django which I use > in server side don't accept this. So I have to change the rpc method's > name "connect" method in AccessManager. > I think it's not bug, because it should works with qcl-php. Should I > report it in bugzilla? >
Yes, please. I'd like to support other backends, too. C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/qcl-access-demo-application-tp6295025p6410720.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
