vibrant 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.
That's a very good decision! > 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)? It's possible and easy to do this as regards Weblocks. However depending on the number of long-polling clients and on whether you have a 32 or 64 bit machine you might have to write an alternative to the thread-based taskmaster in Hunchentoot. > 2. what is the ORM/database layer that is preferred for weblocks and > consistent with it's design patterns and core ideas? It depends on the project. We have backends for Elephant (OODB), Prevalence (persistent in-memory database), Postmodern (Postgres ORM) and CLSQL (generic SQL ORM). > 3. how hard will it be to build/integrate neat widgets like > autocompleters, tabs, datepickers and so on with weblocks? Easy. > 4. what else am I missing that I will need to build in order to create > a complicated interface with weblocks? Hard to say. This depends entirely on what application you're writing. Give me a couple of details (confidential in a private mail if you prefer) and I shall try to make an effort of guessing better. :) Leslie -- 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.
