Web applications unification

Joakim G. jocke@REDACTED
Tue May 27 23:15:07 CEST 2003

Mikael Karlsson wrote:

>tisdag 27 maj 2003 13:36 skrev Ulf Wiger:
>>On Tue, 27 May 2003, Mikael Karlsson wrote:
>>>So why not set some kind of standard interface or framework
>>>to build it on?
>>>- 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.
>Yes, hmm this means that one should use generic behaviours like 
>gen_server etc. in such a framework? 
>I noticed that xmlrpc uses generic behaviours in the latest version (1.13),
>but I can not find any "-behaviour(gen_server)" statement in the code.
>How is that?

The server part of the xmlrpc lib _behaves_ as a gen_server it isn't
written using a gen_server behaviour though.

Like this:
as in:


More information about the erlang-questions mailing list