<div class="gmail_quote">Thanks @Marc, for taking time to reply this this mail.</div><div class="gmail_quote"><br></div><div class="gmail_quote">On Fri, Jul 29, 2011 at 5:38 PM, Marc Worrell <span dir="ltr"><<a href="mailto:marc@worrell.nl">marc@worrell.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">It mostly depends on what kind of web development you want to do.<br>
<br>
Is it more of a mobile application than a publishing web site?<br></blockquote><div><br></div><div>One of the avatars in likely to be a mobile application, but it is neither the first one, nor the only one.</div><div>However, I am not sure I can classify it as a general publishing site, i.e. same content isn't viewed by several people, rather content uploaded 'somehow' (many ways, many sources) is visible only to the user. What the user can view/has viewed, must be held in tight secrecy. Even admins shouldn't be able to view the content or what content users viewed. User can (in-frequently) share some of the content with others, but I'd say that less than 0.1% of the content (figuratively speaking).</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Does is have specific authentication schemes?<br>
Etc. Etc.<br></blockquote><div><br></div><div>Honestly, haven't given this enough thought. One of the requirements is to ensure privacy of user data, and that of the interaction. I'm yet to figure out the "how" part.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">When your project involves a "normal" dynamic website with publishing, users, some interaction etc. then Zotonic might be a good fit.<br>
At least it will prevent you re-inventing quite some wheels. It also uses webmachine, so adding your own specific REST interface should be easy.<br></blockquote><div><br></div><div>Zotonic seemed very interesting, based on a superficial read of the site (I admit, haven't downloaded or tried it), but what seemed a bit intimidating from a newbie standpoint was that I couldn't figure out anything in documentation (s.a. a tutorial) on how to not-use-Zotonic-as-a-CMS-but-as-a-framework. For instance how to write an app that leverage some framework-features of Zotonic, but is largely a REST application. I can understand that such usecase may not the priority for the Zotonic team at the moment. </div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">When your project is really more backend like and not using templates (think of the backend for a mobile app) then it is better to make a server with Webmachine (and whatnot) and use Javascript on the user agent (or a native implementation).<br>
</blockquote><div><br></div><div>If the initial access mechanism to the service/application is desktop browser based is there anything that makes the jQuery + JSON + RESTful backend, harder, less suitable, higher complexity, lower performance, difficult to scale (or any other foreseeable challenges), compared to the template based approach ?</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5"><br>
On 29 jul 2011, at 13:52, Dmitry Demeshchuk wrote:<br>
<br>
> Many people prefer using Erlang just for REST API and internal<br>
> distribution, and serve any user-visible content using<br>
> Python/Ruby/PHP, often on top of some framework (Django, Pylons,<br>
> Rails, etc). For instance, Heroku and Github use Erlang for internal<br>
> stuff, and serve content using Ruby. At Mochi Media, we use Python for<br>
> displaying the pages, and use Erlang only as REST applications.<br>
><br>
> I don't claim this way to be more correct than using<br>
> Nitrogen/Erlydtl/whatever, but the reason why people do that is<br>
> because they don't like using Erlang for pages generation.<br>
> So, you can keep searching, but keep in mind that using another<br>
> language for serving pages isn't that bad.<br>
><br>
> On Fri, Jul 29, 2011 at 3:18 PM, Icarus Alive <<a href="mailto:icarus.alive@gmail.com">icarus.alive@gmail.com</a>> wrote:<br>
>> Hi,<br>
>><br>
>> Looking for some suggestions on how to get started with Web<br>
>> development in Erlang.<br>
>> My background is largely C/C++ systems development, and picked up some Erlang,<br>
>> i.e. I can understand most not-too-complex/large Erlang programs given<br>
>> a little time,<br>
>> unless very esoteric style is adopted, and still find it a bit hard to<br>
>> 'think in Erlang'<br>
>> (a decade of procedural and OO thinking often gets in the way). However, with a<br>
>> turn of events, now I need to do some web-development.<br>
>><br>
>> Started looking at Nitrogen, but finding the syntax very hard. A steep<br>
>> learning curve.<br>
>> I've done some PHP programming a decade back, and found it to be very simple,<br>
>> and this seems almost like a herculean learning exercise. The<br>
>> tutorial, didn't seem<br>
>> to be structured in a beginner friendly way, and there is hardly any<br>
>> alternative tutorial<br>
>> available. So I wonder as to how many people are really using it. I've<br>
>> had a look at<br>
>> Zotonic as well, but not sure if that might be easier / simpler, and<br>
>> also if it'd be<br>
>> too-much work separating out the CMS from the framework, it might be<br>
>> bit too hard<br>
>> for a beginner to make reasonable progress.<br>
>><br>
>> My preferred approach would be to keep the backend pretty much REST'ish and use<br>
>> heavier frontend (s.a. jQuery) to interact with it, although I've the<br>
>> need for delivering<br>
>> some streaming media, and strong authentication etc. Also, I shall the<br>
>> services to be<br>
>> available on mobile handsets.<br>
>><br>
>> Would really appreciate if someone can share thoughts, advice, and pointer to<br>
>> good / comprehensive tutorials etc., to make this learning (&<br>
>> adoption) as simple and<br>
>> easy as possible. Alternatively if someone feels that sticking to PHP<br>
>> (which I am slightly<br>
>> more comfortable with) would be a good idea, shall be happy to have that vote<br>
>> of confidence.<br>
>><br>
>> Icarus<br>
>> _______________________________________________<br>
>> erlang-questions mailing list<br>
>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> Best regards,<br>
> Dmitry Demeshchuk<br>
> _______________________________________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>regards,<br>Banibrata<br><a href="http://www.linkedin.com/in/bdutta">http://www.linkedin.com/in/bdutta</a><br><a href="http://twitter.com/edgeliving">http://twitter.com/edgeliving</a><br>