|
|
| 2003-01-15 |
Rerendering API |
|
Tools with background rendering can now implement a rerender method. If they do, they show up in the upstream tool in the overview. There you can select them and trigger a rerendering of the content. This is especially usefull when templates have changed, as you can update your full website with one click. |
|
posted at 17:38:24
#
|
| |
|
|
Installation description, actually this is just the content of the INSTALL-FROM-SOURCE file. |
|
posted at 16:08:48
#
|
| |
|
SOAP is now fully integrated as an alternativ way to call remote procedures. This is done with a patched version of SOAP.py (patched version 0.97 to enable encodings in much more places than was possible with the shelve version). You now can do the same calls you can do with XML-RPC with SOAP. An example:
import PyDS.SOAP
srv = PyDS.SOAP.SOAPProxy('http://localhost:4334/SOAP')
for el in srv.weblog.getRecentPosts('user','passwd'):
print el['title']
The same restrictions apply to SOAP calls as apply to XML-RPC calls, so only positional parameter passing works.
For RPC calls there is a shortcut calling mechanism implemented, as is a simple introspection mechanism. You can change the SOAP or RPC2 access point in the URL as follows:
import PyDS.SOAP
weblog = PyDS.SOAP.SOAPProxy('http://localhost:4334/SOAP/weblog')
for el in weblog.getRecentPosts('user','password'):
print el['title']
This makes the code more readable, as it looks much more like internal methods. To use the introspection feature, you can call a special method listRegisteredFunctions. This method never needs authentication, so you just call it without any parameters. Either with the shortcut version or the longer version. The method returns all method names that are available, it's actually much like the internal dynamic Documentation. |
|
posted at 15:32:32
#
|
| |
Important Bugfix |
|
The 0.1 Alpha has an important bugfix that might pose some small problems with upgrades, but is important nontheless. The problem is, Radio only transmits the md5 hexdigest of the password, not the actual password. So Python Community Server expects this, for example in the login.py module. Python Desktop Server did send the actual password and not the hexdigest. This worked, because Python Desktop Server stores what it gets. But so Python Desktop Server users couldn't login on the web, because their password was wrong.
This is now fixed, but this needs some work. You have to do the following steps:
- upgrade the version (redownload archive)
- call your community server admin to set your password anew, as it is stored wrong!
- go to the upstreaming settings and reenter your password to set it correctly within Python Desktop Server.
The admin can set the password on the Python Community Server with two methods: either stop it and use changepasswd.py, or use the (new, so upgrade before trying!) pyds-admin method password. |
|
posted at 12:18:24
#
|
|
|
This is the Python Desktop Server weblog.
 (Donations will be used by the author to buy stuff, fullfill selfish wishes or do other silly recreational things. You have been warned.).
The PyDS is
|
