> Haxe seems to be great, and very well done. But there are some things > that makes me want to wait before developing on haxe: general public > adoption, success cases, the problem that it would be necessary to teach > this new language to each person that would want to join me in the > future, the current tools developed that would need to be ported…
Teaching/Learning haXe is something very easy if people already know about AS2/AS3. The Flash API is the same. haXe will soon support Flash9. [...] > haven’t, because we knew nothing about how JAVA behaves on the internet: > is it fast? Is it stable? Is it easy to configure? Does it consume too > much server’ resources? Is it easy to find a good http server that > serves JAVA? (Good and.. cheap?) OpenAMF is as good as AMFPHP is? > > What about alternatives? Java is fast but the JVM consume quite a lot of memory. For alternatives, you have haXe which is running on the Server side by using mod_neko for Apache. Watch haXe Remoting tutorials on http://haxe.org/doc > We have developed CastingOffice’s server side in a 2-tier basis, using > PHP. The lowest tier - the database layer - is responsible for executing > SQL queries on the database. The second tier is responsible for business > controlling and data consistency. And we have a “+1” half-tier, that > exposes the business layer to the outside, using AMFPHP. We haven’t > used any design patterns, since our purpose was mainly to achieve what > the service was intended to (SOA). My question is: what do you normally > do server side? Just one layer (the service), and directly access the > database? N-tier development? Or you go further, and apply design > patterns to achieve a more structured application? In other others, is > it preferable a data driven programming (db, our option) or data > persistence (OO)? I know the first one Is far better in efficiency, but > for big applications shouldn’t data persistence be preferred? haXe on the Server has a library for handling OO persistence called SPOD. It's very easy to use and you don't have to write a lot of SQL everywhere. It also support object caching and transactions. Watch http://haxe.org/tutos/spod for a quick tutorial Best, Nicolas _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
