Not to distract from the haXe implementation (I'm sure it's good), but Hibernate used in combination with Red5 could be a good alternative. You would be able to wire up Hibernate with Spring and then use Red5 to connect to your DAO layer with AMF or RTMP.
This is how we are planning on building the Red5.org website. Man, I need to spend some time on that thing soon. :-) -Chris On 9/11/06, Marcelo de Moraes Serpa <[EMAIL PROTECTED]> wrote: > haXe SPOD seems powerful... > > > On 9/11/06, Martin Heidegger <[EMAIL PROTECTED]> wrote: > > > > Java ... Hibernate ... > > > > greetings > > Martin. > > > > > > 2006/9/11, João Saleiro < [EMAIL PROTECTED]>: > > > > > > > > So, you would recommend an ORM System instead? Which one do you use for > > > PHP? And for JAVA? > > > > > > João Saleiro > > > > > > > > > Alex Thurlow wrote: > > > > I have to agree with this. Relational databases are relational for a > > > > reason. If you're in a situation of needing to make the same queries > > > > constantly I have to recommend memcache: > > > > http://www.danga.com/memcached/ > > > > > > > > We have this running between our php site and our postgres database. > We > > > > can handle many times more traffic than we would be able to normally. > It > > > > takes a little bit of dev work, but is worth it entirely. > > > > > > > > -Alex > > > > > > > > Alias™ wrote: > > > > > > > >> I have to say, I'm not sold on OO databases. > > > >> > > > >> Databases, ultimately, need to be two things - accurate, and fast. > > > >> > > > >> Generally, OO means trading performance for maintainability - in the > > > >> case of code, that's a substantial gain, but I'm not so sure that's > > > >> going to necessarily apply as much to data. Large databases need > > > >> constant care and maintenance, and I'm not sure that OO would add > > > >> significantly reduce the need for that - IANADBA, but I suspect the > > > >> opposite. Why do you think DBAs are among the most highly paid IT > > > >> workers? > > > >> > > > >> Obviously it would be nice to store data in a nice object format, but > > > >> why should the database under that have to conform to that if it's > > > >> going to be less efficient? A slow database is the kiss of death to > > > >> any web app. Using some kind of middleware to serialize the data into > > > >> table format seems like the best approach to me. > > > >> > > > >> Alias > > > >> > > > >> > > > >> > > > > > > > > > > _______________________________________________ > > > osflash mailing list > > > [email protected] > > > http://osflash.org/mailman/listinfo/osflash_osflash.org > > > > > > > > > > > > > > > -- > > ICQ: 117662935 > > Skype: mastakaneda > > _______________________________________________ > > osflash mailing list > > [email protected] > > http://osflash.org/mailman/listinfo/osflash_osflash.org > > > > > > > > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > > > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
