Web applications unification
Ulf Wiger
etxuwig@REDACTED
Tue May 27 13:36:29 CEST 2003
On Tue, 27 May 2003, Mikael Karlsson wrote:
>So why not set some kind of standard interface or framework
>to build it on?
>
>Like:
>- http server: Yaws
>- http client: inets (originally jnets) http.erl
>- ODBC, Corba etc: Erlang/OTP
>- application control/configuration: Erlang/OTP
>- authentication: eldap ?
>- XML: xmerl
>- XML-RPC: xmlrpc (with interface to yaws and inets/http client)
>- SOAP: idx-soap (with interface to yaws and inets/http client)
>
>I think most things are (almost) in place to build a
>*really good* web application framework with Erlang.
I agree. I also added 'builder' to jungerl as an attempt to
provide a lightweight aide for packaging OTP applications
and building start scripts. I don't know how well it
succeeded (and it does need more work).
The general idea was that you should be able to
incrementally build more and more complex systems with
relative ease.
/Uffe
--
Ulf Wiger, Senior Specialist,
/ / / Architecture & Design of Carrier-Class Software
/ / / Strategic Product & System Management
/ / / Ericsson AB, Connectivity and Control Nodes
More information about the erlang-questions
mailing list