Here is the blog of KI RUS developing news.
We will describe there our complicated problems, with solutions (or without).
Lets begin with Local arKItect version.
The beta version was almost finished by our "server-dev-guru", and already delivered for trying but ...
we found on Tuesday that it didn't work on Konstantin`s computer. It works on Paul`s, Dmitry`s Andrew`s and virtual ones but not on Konstantin`s...
We constructed a detailed log for both server and client side ... but it didn't show exact problem, only gave the http error code #12031 in WinInet.
After deep investigation we found, that the 'server side' for local version is not good enough, and updated it to be equal to MSDN example... but the problem still remained, in a new form.
Then we setup the stream sniffer (SocketSniff, the standard one Microsoft Network monitor didn't help!) and looked on the problem from another side .. but it still didn't help.
After surfing the Internet, in the MSDN article (http://msdn.microsoft.com/en-us/library/system.net.sockets.networkstream.read(v=vs.90).aspx), in small community comment (existing only in one version of this article) we found a small key... on Thursday. Not everyone agreed with proposed solution, it was kind of internal battle. But finally it helped.
All four of us was involved to investigation during those terrible days (about two full day for each one).
Fortunately the solution was found before we got completely exhausted, and we got new practial knowledge (as usual).
We will describe there our complicated problems, with solutions (or without).
Lets begin with Local arKItect version.
The beta version was almost finished by our "server-dev-guru", and already delivered for trying but ...
we found on Tuesday that it didn't work on Konstantin`s computer. It works on Paul`s, Dmitry`s Andrew`s and virtual ones but not on Konstantin`s...
We constructed a detailed log for both server and client side ... but it didn't show exact problem, only gave the http error code #12031 in WinInet.
After deep investigation we found, that the 'server side' for local version is not good enough, and updated it to be equal to MSDN example... but the problem still remained, in a new form.
Then we setup the stream sniffer (SocketSniff, the standard one Microsoft Network monitor didn't help!) and looked on the problem from another side .. but it still didn't help.
After surfing the Internet, in the MSDN article (http://msdn.microsoft.com/en-us/library/system.net.sockets.networkstream.read(v=vs.90).aspx), in small community comment (existing only in one version of this article) we found a small key... on Thursday. Not everyone agreed with proposed solution, it was kind of internal battle. But finally it helped.
All four of us was involved to investigation during those terrible days (about two full day for each one).
Fortunately the solution was found before we got completely exhausted, and we got new practial knowledge (as usual).
No comments:
Post a Comment