There is no little out there on this new concept, but luckily the latest MSDN magazine had an article on this. The power of the asynchronous page is that it allows you to release the thread that is executing your page request during long operations (i.e.: web service calls). Once the call is complete, it will go out and grab a new thread from the pool and finish the requet. This will allow for a large performance increase in our application since threads aren't blocking waiting for a rate shop to come back.
Any how, there are numerous examples on how to use the async methods built into the web service proxy to make this work. The real question is how do we create our own async methods since our web service calls are inside of a wrapper class.
I've got a copy of the MSDN Magazine sitting on the shelf if you are interested in reading it or you can probably find it online somewhere. This is definitely something we will want to implement in our Reservations project.
Read the complete post at http://www.dotnettipoftheday.com/blog.aspx?id=65