At work I’ve been working on prototyping the new architecture for our edge server management system. We want to move away from a strictly PHP/MySQL architecture to a more flexible one that allows us to interface from native graphical clients, the web, command-line, etc. So I wrote a simple class representing user management and wrapped it in a Mono Web Service. For now the class saves and loads its data by serializing/deserializing itself as XML and creates its /etc configuration data by processing an XSLT stylesheet. I then wrote a graphical client in Gtk# which runs on Linux and Windows.
Mono makes this stuff so easy to do once you know a bit. The hard part for me now is the larger technical decisions: what data store to use, design the validation/error checking, etc. I’m definitely excited about moving in this direction though. I have nothing against PHP/Mysql, but the web interface we were forced to use was far too limiting.
Tags: Mono
August 13th, 2004 at 8:05 pm
You should have looked at XUL (as in server/PHP generated) - Almost all the advantages of a desktop client, with a smaller install footprint, and good ole PHP Rapid prototyping/development.
August 14th, 2004 at 2:02 pm
XUL is pretty sweet, but I don’t think it quite fits our requirements. We want a common set of interfaces for managing the edge server from anywhere. In other words, from any web browser (IE included which 99% of our resellers will be using), the command line, a native graphical client, etc.
August 24th, 2004 at 9:25 am
Do you have some resources (link, pdf) about writing webservices with mono? I’ve already read the mono handbook (shipped with monodoc)
I’m also searching a way to use .NET webservices with java or c++ (or php).
I think like you that web interface are very limitative in comparison to native applications.
August 24th, 2004 at 9:45 am
Maybe a book such as this:
http://www.charlesriver.com/ti.....bserv.html
would help.