This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
This is related to my other post, but I thought it might make more sense to start a new thread... I'm interested to know how your library does web requests to SDB. There are two ways, sync and async. Async would use BeginGetResponse and EndGetResponse and use IAsyncResult. Sync would simply do an HttwpWebRequest and block until the response is received. The Async pattern is documented with a good sample here: http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.begingetresponse.aspx. I think that even though your app currently needs to get the NextToken to chain requests, the requests themselves should still be executed asynchronously. I'm hoping you agree and have a good pattern for doing so. I'm no expert on async programming in NET but I do know enough to know that it can be difficult to get right. See this old article for example about it (as it applies to ASP.NET) http://msdn.microsoft.com/en-us/magazine/cc164128.aspx. Hopefully the situation has improved. Interested to know your thoughts.
|
|
|
|
|
We actually delegate all the Web service invocation to the .NET wrapper library provided by Amazon. This, I'm afraid, uses the synchronous GetResponse method rather than the async method pair. We agree that using the async methods would be more efficient but for maintenance reasons we are reluctant to fork the Amazon library unless our customers identify a compelling use case for the async implementation. |
|
|
|
