On Jul 12, 8:57 am, Nandan Bagchee <[email protected]> wrote: > > I have a pretty big project written in Python/Django, but I got pretty > > tired of Python and I want to move to a more productive environment. > > Without making this OT, I thought Django was considered very productive? > Somehow lately I've been hearing more negatives about it..
It is productive compared to doing everything by hand :) But, at least conceptually, weblocks seems to be handling a lot of stuff that Django doesn't handle (like workflows, ajax, components). > > > So I'm considering two solutions: > > 1. Clojure + Vaadin + some ORM > > I semi-evaluated Vaadin some while back. It is promising, and has a similar > philosophy to weblocks -- everything is done at the backend using seamless > ajax, so malicious manipulation at the front end is less effective. In terms > of baked in widgets etc. Vaadin is quite complete, far more so than weblocks > is. It wasn't really an option because we didn't want to work in java. > Perhaps you could evaluate how easy it would be to extend with custom > widgets (and hey, while I'm at it how about a tutorial? ;-) Tomek Lipski recently posted a simple integration tutorial here: http://dev.vaadin.com/wiki/Articles/ClojureScripting So based on that I put it together and you just call the Vaadin Java classes from Clojure and that's basically it, I didn't do much more. I don't know how to extend it with custom widgets, that's probably in the Vaadin book. > > But it's a hard decision so I wanted to ask you the following > > questions: > > 1. is it easy/possible to implement long poll for continuous updates > > of content from the server to the client in weblocks (for a chat > > feature, and similiar)? > > I would suggest using node.js for comet-y kind of scenarios. Otherwise at > any significant load you'll have issues. But node.js doesn't have anything to do with CL or weblocks does it? Thanks for the rest of your reply, acknowledged ;) -- You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en.
