Not sure what XML-RPC gives you that something like, oh, say, PostgreSQL wouldn't. Maybe you save some RAM or something. But damn, RAM is cheap compared to my hourly rate. as for browser crashes, I've never had so many since switching to 5, even on an Athlon 3000+. Seems to be the worst if you import a 4.021 config.
I'd be curious to see how many of us out there actually get a page when in Intrusion Protection >> Rules >> expand Miscellaneous WWW-specific rules >> then click Show All.
It also seems a bit asinine to force Astaro to Read through everything just filter out what you dont want. Again, why not just run SQL queries for what you do want to see in a web page.
We can make him faster, stronger, better - We have the technology!
Don't mis-understand me totally here though, between the things that needed fixing from 4 and the added functionality, 5 is the Premier FW OS. I just feel like I've given up two toes for a new pair of shoes.
Where's there's smoke there's fire, and it appears there's now a fire @ https://demo.astaro.com It seems to be producing the same Internal Server Error page that I get on my systems from time to time when the webadmin interface craps out only there's no refreshing this one to 're-login'.
The problem with the pop-up/flooting menu is major and I for one need a fix before I can use 5. I use an 800x600 display and the machine I test from has IE5. By default I can not see anything below IPSec on the Reporting menu (if I clear everything, URL, menu, etc. I can get down to the HTTP Proxy).
I'm sorry to hear about the speed issues and will have to test that since I administer all of my live ASL systems remotly.
Some explanation about XML-RPC for all that seem to think to know all about it. XML-RPC is a layer ABOVE the storage layer and acts as a Remote Procedure Call layer not as a DBMS system. An application exposing an XML-RPC interface may as well be running an SQL database but that is not (and should not be) important to the caller.
I am still interested in knowing whether the XML-RPC structure will be made available so that remote systems could be written to write and read data from the configuration manager. This could allow third parties to write some very interesting additions to Astaro. The best example I can think of would be to integrate corporate address books (say from an LDAP server) into the Astaro spam whitelist.
one of the reasons for introducing such a mechanism is to be able to connect different config clients to the firewall independantly of platform language or OS. Currently there is no API to do so but it is planned.
