1

I was reading a couple of articles on how to use Yaws in a RESTful way, how Webmachine maps HTTP semantics to resources and all of them helped a lot to grasp the concept.

This is the point where I got confused: it seems like that Webmachine as a good REST toolkit and Yaws as a mature web server would complement each other instead of writing a REST implementation each time but I had found no trace of these tools being used together. The only relevant google hits were Steve Vinoski's twitter and his github experiment.

I am fairly new to OTP (and Yaws, web development etc) and I might be missing something. Webmachine is a full OTP application, bundled with Mochiweb so my guess would be that it is an overkill but that's just a shot in the dark.

(I know Cowboy has its own REST implementation too but Yaws is more appealing to me and REST is not always a necessity of course.)

Community
  • 1
  • 1
toraritte
  • 6,300
  • 3
  • 46
  • 67
  • 1
    There's been little interest in my Webmachine + Yaws fork, so I never pushed to get the necessary changes into Webmachine master. It could still happen, though, given that discussion about it seems to be coming up more frequently these days. – Steve Vinoski Aug 16 '15 at 00:06
  • Thanks, at least I know that I am on the right track. Basically you could extract the main Webmachine logic to use it with any server, right? (I guess you already did it because your fork mentions Cowboy as well but I still need to get used to erlang/OTP) – toraritte Aug 16 '15 at 00:35
  • 1
    Webmachine contains numerous assumptions about Mochiweb. My fork, which is out of date at the moment, removes all those assumptions and replaces them with a portability layer that hides the underlying web server. – Steve Vinoski Aug 16 '15 at 01:00

0 Answers0