|
Another bunch of changes in the CVS. The main two changes are in the area of authentication and in the area of WSGI support. Yes, TooFPy now has a WSGI container where you can put in your applications. If you want, you can then use direct tool calls in your WSGI application to make use of the many TooFPy features, or you can stay fully in WSGI world and so be portable to other python servers.
The changes in authentication are that now there is not only the rather heavywheight RSA authentication, but support for IP based authentication and HTTP basic authentication for RPC calls, too. Those are rather easy to set up, so if you don't need the full blown public key authentication stuff, you can now have a simpler way to restrict access. Clients can be grouped now, so you can write your tools against some groups instead of maintaining client name lists for all allowed clients within the tool itself.
Another bigger change now is that the two special medusa http handers for the /API/ and /WSDL/ namespace are gone - and reborn as real tools. This makes some stuff easier to maintain and is more logical. The WSGI handler is built as a tool, too.
A side effect of the API and WSDL change is that now the transient tools and factory tools are actually tested and actually working - nobody seems to have used them before, because nobody complained about them not working. On the other hand, maybe nobody used them because nobody knows how 
|
