I think that there are other frameworks that are as difficult to get up to speed with/throw up incomprehensible errors or are just a pain in the back to work with. Fortunately, Erlyweb is not one of them. That is not to say that it is to be encouraged, but I think that erlyweb is still comparatively pretty young and has got a lot more coming with time.
But even in this state that it is in, it still delivers a lot of value. I was once working on a facebook app and having tried Java, RoR and scala, I gave up in sheer frustration and erlyweb/Brian Fink's facebook lib saved the day. So hang in there if you want to benefit from this. Nii Amon On Sep 27, 9:09 pm, Steve <[EMAIL PROTECTED]> wrote: > Given a task to implement a quick web service, I thought I'd try > erlang/yaws/erlyweb to build it. Reading the fluff, it seems this > should be "easy" and "fast" to do. > > 1) Yaws didn't install right on the development platform available > (windows). I read the yaws documentation completely but in the end I > had to piece it together from digging around in the yaws code to > understand the structure of yaws to get a decent install. > (time wasted: approx 3 hours) > > 2) Again, there wasn't *any* correct documentation to explain how to > connect to the required database (postgres) but fortunately I found > this blog > post...http://cdrinpeace.wordpress.com/2008/06/09/configuring-erlyweb-with-p... > (time wasted: approx 2 hours) > > 3) With everything supposedly running correctly, I finally got the > error message below (returned from postgres). Again scanning at code > level I found that this is a problem not with the driver (psql) nor > erlyweb but in the erlydb code itself (i.e. erlsql -- the error > message below should be more than sufficient to find/fix the problem > if you have the time/interest). Short of rewriting the platform code > (!!not acceptable - we cannot be expected to maintain a branch of the > erlang code!!), or waiting for an official fix release (there is > little doubt this would be outside our schedule) this ended up as a > project blocker. > (time wasted: approx 2-3 hours) > > Result: Having wasted essentially a DAY on this, I gave up and used > Tomcat instead. > > LESSON LEARNED: Given that achieving even the simplest project runs > into all sorts of delays, It should be OBVIOUS why erlang/erlyweb is > not hot news for web developers/web development!!! > > The final straw was.... > > ERROR erlang code crashed: > File: appmod:0 > Reason: {function_clause, > [{lists,foldl, > [#Fun<erlydb_psql.2.79238577>,[], > {sql_error,"42601", > "Rbase_yyparse L5868 Fgram.y HUse separate LIMIT > and OFFSET clauses. MLIMIT #,# syntax is not supported"}]}, > {erlydb_psql,get_select_result,2}, > {erlydb_base,select,3}, > {erlyweb_controller,list,3}, > {erlyweb,ewc,2}, > {erlyweb,handle_request,6}, > {yaws_server,deliver_dyn_part,8}, > {yaws_server,aloop,3}]} > Req: {http_request,'GET', > {abs_path,"/namelookup//agent/list/1"}, > {1,1}} --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
