|Subject||RE: [Firebird-Architect] Strategic Replacement for Services API|
|Author||Claudio Valderrama C.|
> -----Original Message-----Can you explain more about this named service? I don't get the idea yet.
> From: Firebird-Architect@yahoogroups.com
> [mailto:Firebird-Architect@yahoogroups.com]On Behalf Of Jim Starkey
> Sent: Miércoles, 27 de Julio de 2005 18:37
> The adminstation
> server parses and validates the XML, then dispatches to a named
> service. The result of a request (or reasons for failure) would be send
> back to the front as XML.
> The split between front and back end using XML as request protocol is aWe already have a multi-platform C++ GUI in progress: FlameRobin, so it
> very easy, robust, and extensible technology -- basically anything can
> be passed either direction. If I were doing it, I'd create a Window's
> GUI in C++ for the front end and C++ for the administration server. I
> have a lifetime ambition never to do another Unix GUI, so if we go that
> path, it's either Wine or somebody else's front end.
could serve as the reference implementation.