| Author |
Message |
< Erlyweb mailing list ~ Strengths/Weaknesses of Erlang for Web Apps |
| Willem |
 Posted: Sat Nov 24, 2007 2:27 pm |
 |
|
|
User
Joined: 21 Jul 2006
Posts: 59
|
I hope this isn't too much off topic, but I would like to comment on
this:
> I'm aware that it's possible to use Yaws+erlsom, but it has a few
> weaknesses:
> - erlsom's install relies on sh; it doesn't install on Ubuntu without
> a bit of mucking around, and must be a challenge for Windows as well
Actually, installing erlsom on windows is quite easy: download the tar-
ball from sourceforge, unzip it and compile it (in the erlang shell:
make:all([{outdir, "../ebin"}, load]). ). Or you can get it from CEAN.
I guess that would work for Ubuntu as well.
If there is any advise on how to make erlsom easier to install I would
be interested to hear it - after all it would be a pity if the code is
not used for reasons like this.
> - setting up a Web service is a non-trivial exercise; just read
> through the relevant page (http://yaws.hyber.org/soap_intro.yaws) at
> the Yaws site
I sort of agree to this comment: it is more complex than necessary -
but it would be easy to fix this.
At this moment I am trying to contact the people who maintain erlsoap,
to see whether I can persuade them to incorporate some changes that I
made. It would be fairly straightforward to do the same for yaws, I
think. I focussed on erlsoap because it seems to be more lightweight
and easier to install.
In the proposed erlsoap version, all that you have to do to set up a
soap service is:
intsallation: install erlsoap & erlsom (from CEAN, for example)
development: create a callback module for your soap service (1 module
per WSDL). It needs to implement 1 function, called handler. This
function will be called when a SOAP service from the WSDL is called.
Its most important argument will be the body of the SOAP request,
conveniently translated to a structure of records. The handler
function should return another structure of records that corresponds
to the body of the response.
deployment: start httpd (comes with the standard distribution). In the
configuration file, make sure to start mod_soap, and for each WSDL
file include a line that links the WSDL to a URL and to the callback
module.
Does erlyweb use yaws? If so, I would be happy to help with the
creation of a similar appoach for yaws. Would it need further
integration with erlyweb?
Regards,
Willem
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
 
|
| Guest |
| Posted: Sun Nov 25, 2007 12:47 am |
|
|
|
Guest
|
Thanks Willem,
On 25/11/2007, Willem de Jong <w.a.de.jong@gmail.com> wrote:
>
> I hope this isn't too much off topic, but I would like to comment on
> this:
>
> > I'm aware that it's possible to use Yaws+erlsom, but it has a few
> > weaknesses:
> > - erlsom's install relies on sh; it doesn't install on Ubuntu without
> > a bit of mucking around, and must be a challenge for Windows as well
>
> Actually, installing erlsom on windows is quite easy: download the tar-
> ball from sourceforge, unzip it and compile it (in the erlang shell:
> make:all([{outdir, "../ebin"}, load]). ). Or you can get it from CEAN.
> I guess that would work for Ubuntu as well.
>
I actually only "discovered" CEAN a few days ago - until then I'd been
mucking around compiling stuff in Ubuntu, and basically not needing to
use Windows. When I hit a situation where I had to work on Windows, I
quickly got frustrated with the lack of Unix utilities, stumbled on
CEAN, and have been happily using it since.
> If there is any advise on how to make erlsom easier to install I would
> be interested to hear it - after all it would be a pity if the code is
> not used for reasons like this.
>
> > - setting up a Web service is a non-trivial exercise; just read
> > through the relevant page (http://yaws.hyber.org/soap_intro.yaws) at
> > the Yaws site
>
> I sort of agree to this comment: it is more complex than necessary -
> but it would be easy to fix this.
>
> At this moment I am trying to contact the people who maintain erlsoap,
> to see whether I can persuade them to incorporate some changes that I
> made. It would be fairly straightforward to do the same for yaws, I
> think. I focussed on erlsoap because it seems to be more lightweight
> and easier to install.
I vaguely remember reading a message a while back where the person
writing it said he'd not been able to contact the erlsoap
maintainer/s. It doesn't look like it's been updated for quite a
while, so maybe that person has just dropped off the map.
>
> In the proposed erlsoap version, all that you have to do to set up a
> soap service is:
> intsallation: install erlsoap & erlsom (from CEAN, for example)
> development: create a callback module for your soap service (1 module
> per WSDL). It needs to implement 1 function, called handler. This
> function will be called when a SOAP service from the WSDL is called.
> Its most important argument will be the body of the SOAP request,
> conveniently translated to a structure of records. The handler
> function should return another structure of records that corresponds
> to the body of the response.
> deployment: start httpd (comes with the standard distribution). In the
> configuration file, make sure to start mod_soap, and for each WSDL
> file include a line that links the WSDL to a URL and to the callback
> module.
That sounds very elegant - exactly the sort of thing I'm looking for.
>
> Does erlyweb use yaws? If so, I would be happy to help with the
> creation of a similar appoach for yaws. Would it need further
> integration with erlyweb?
erlyweb uses yaws as a platform - essentially erlyweb provides a
vaguely Ruby-on-Rails-like MVC architecture on top of yaws. MVC is a
particularly good fit for a lot of Web apps; I've used Rails a lot,
but have been hitting on its scalability limits lately.
One thing I like about Rails is that it's almost trivial to add SOAP,
XMLRPC, JSON, ... interface to existing functionality. It's literally
about a 10 minute job in most cases.
Yariv said a few days ago that he was going to look into adding
support for Web services to erlyweb. Maybe the two of you could get
together to talk things over. I'd happily test any such solution you
come up with - I've got a project on the go now that's perfect for it.
Regards
Dave M.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Nov 25, 2007 1:17 am |
|
|
|
Guest
|
>
> One thing I like about Rails is that it's almost trivial to add SOAP,
> XMLRPC, JSON, ... interface to existing functionality. It's literally
> about a 10 minute job in most cases.
I think this would be a nice feature to add to ErlyWeb -- not just
SOAP, but a generic RPC capability that abstracts away the protocol
and lets you write handlers that work with multiple protocols without
having to write extra code.
ErlyWeb already maps URL requests to their controller functions. What
needs to be added is
1) Map other types of requests, e.g. SOAP, to their controller functions.
2) Define common return values and implement their translations to
different protocols. Ideally, the RPC handler would figure out
automatically which protocol to translate the return values to based
on the request -- there would be no configuration involved (except for
maybe enabling/disabling protocols).
If Erlsom already implements SOAP and it's not too difficult to
integrate I'd rather use it than write a SOAP handler from scratch.
If you have any thoughts on how to do this please share them.
Thanks,
Yariv
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "erlyweb" group.
To post to this group, send email to erlyweb@googlegroups.com
To unsubscribe from this group, send email to erlyweb-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
Post recived from mailinglist |
|
|
| Back to top |
|
| wailian |
| Posted: Tue Mar 20, 2012 2:52 am |
|
|
|
Guest
|
| One of them is the Ugg bailey button boot which has classic and uniquely designed buttons on its body to give that elegant and luxurious look. It has a fantastic look and this includes the Bailey Triplet Boot which has 3 buttons. These boots have a shaft (the upper part of the boot) which can be turned up or turned down depending upon your need. These buttons are both for style or decoration along with being functional or usable as well. |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
