"一首诗" <[EMAIL PROTECTED]> writes: > how to make an asynchronous process synchronized without having any > tight loops?
Just call for the results and wait for it to be returned. If you have too many calls them you'll have to support too many connections to the database and the ammount of data being handled. > Or how did they made it possible to make db operation just like a > function call without considering any asynchronoused problem? It is easier to deal with synchronous stuff than asynchronous stuff... > Where could I save the socket which would be used to communicate with > the remote server? It will be awful to create it each time I need it? Explain what you're willing to do. If it is a database server you'll probably end up with a connection pool. This makes it better to reuse idle connections. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
