> > No I don't actually. I just checked the code that did it, and it uses a > > thread and the threaded api, which is ugly. The comments in that code > > indicate the author thinks it sucks too, and suggests to use a real > > database... > > I've been hearing that a lot....
I get that feeling whenever I use mysql ;-) > > I'll have another look later, and see if I can find the magic. > > Cool, thanks. No luck in todays search. It's a frequent question however... I'll be away for a few a week or so, so I probably won't find anything soon. > > > A URL for async PostgreSQL would be useful too. > > > > PostgreSQL is easy: > > > > http://www.postgresql.org/docs/8.1/static/libpq-async.html > > > > PQsocket is the magic one, then just select/poll (or use > > ecore_fd_handler_add ;-) > > Ahh, excellent. It looks very similar to what I had hoped for. It's quite nice. I've written a very high performance server using the postgres api, and it lends itself to it beautifully. If you are really good, you can fire off multiple requests at once, and retrieve them one-by-one - which can be really useful. > As for the event/select loop, I haven't decided which (if any) I will use. It > certainly will not change before 0.5.0. eet & evas are now in debian experimental. Ecore has been uploaded. Embryo has a (resolved) licence issue and will be there soon. Once that is in, it should be clear to upload edje - which is all of the things galaxie requires. > > Catch is, will the extra cost of keeping messages in order kill the > > gain? > > I should do. Should be able to process other player's requests while waiting > for the DB to return. It certainly will be more complex though. TP05 may need to drop the in-sequence requirement for messages. Regards, nash _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
