 |
| This version of beWeeVee pretends to be a Technical Demo of what is possible nowadays with the technology that we in Corvalius own. You will find some issues that we're currently working on, and we want to let you know them in order to understand the context of the application. We're planning to launch a new version in the upcoming weeks, so we'll update this list soon. |
 |
We used Windows Communication Foundation (WCF) for the Server and the Client. Silverlight 2 do not support TCP through WCF (something that is available in the current Silverlight 3) so the user may notice the polling that the client does to retrieve events. Following our Guideline of no clever coding, we said ‘no’ to code using TCP native sockets interface on Silverlight 2. |
|
The user may notice that when lots of information gets send (after a
very big paste for example) the other end may notice some slowdown. That is caused by how the insertion operations are performed in the component. Following the Guideline we didn’t separate the shared state from the control; we allowed the control to handle the state by itself. |
|
When you press enter in certain situations because of a known bug we understand that the entire paragraph has been deleted and added again. In most situations this shouldn’t be a problem, but when you couple it with the performance issue for not separating the shared state it gets pretty annoying. Just press F5 to refresh and you will be fine. |
|
The server is preeeeetty small, so if we get too many hits we can guarantee it will fail because of lack of resources. |
|
|
