I investigated the isolate to see if it can support waiting another isolate to finish, then continue the rest of job.
But Dart's concurrency is really restrictive, there seems no way to achieve this.
Considering many poor design of asynchronity of current Dart, server side Dart seems not good option right now.
Maybe I may try 'Go' as well..
Rob pike and Thompson who are behind Go had been working on this area.
http://doc.cat-v.org/plan_9/4th_edition/papers/sleep
Of cause Java is still OK..
If we define some mapping tool from Dart annotation to JPA annotation, it is still not so bad option.But even we use java in server side, lazy evaluation on Dart client is still not possible. As long as the expected job in client side is low, this may not be a big problem though..
No comments:
Post a Comment