Fun, but...
Started on version 2 of Tony's product as mentioned before. I'm doing things Synchronously now and without a web service call so I can get all of the benefits of lazy loading, etc... from NHibernate. But I'm still doing things like initial screen loads, etc... inside a separate thread so that I can still get that same responsive feeling that one gets from an Asynchronous implementation.
I've only written 2 quick pieces of the application and I already feel like there must be a better way :). Creating a Thread manually, then starting it, the calling into a delegate from the Dispatcher to actually update the UI is feeling less fun than it could be.
I think I'm actually starting to miss some of the boilerplate code using a web service provides. But I probably could also abstract a lot of this away. I'm hoping to do things slowly and correctly this time around so I might end up doing that anyway. But it has been fun getting back in touch with dealing with some of the real and fun problems surrounding doing multi-threaded applications the good old fashion way.
I've only written 2 quick pieces of the application and I already feel like there must be a better way :). Creating a Thread manually, then starting it, the calling into a delegate from the Dispatcher to actually update the UI is feeling less fun than it could be.
I think I'm actually starting to miss some of the boilerplate code using a web service provides. But I probably could also abstract a lot of this away. I'm hoping to do things slowly and correctly this time around so I might end up doing that anyway. But it has been fun getting back in touch with dealing with some of the real and fun problems surrounding doing multi-threaded applications the good old fashion way.
Comments
Post a Comment