Here, There, Everywhere...
…but today’s implementation is not ;) Our underlying platform is designed to enable a wide range of scenarios, at broad Internet scale. We closely watch the feedback from our Technology Preview users along with the health and performance of the service, using it to continually improve the system and ramp up our scale.
As we go through this process, we’re hearing your questions about how many folders and files users can put in Live Mesh today. Here’s a quick summary of the upper bounds we’re testing against ourselves at the moment – we’ll expect these numbers to keep going up with subsequent service updates. [UPDATE: these are not limits that are hard coded into the system. They are boundary guidelines we've established based on internal and external feedback, and we're confident that anything under these boundaries will work well for all users. Because they are not hard coded limits, you can exceed these boundaries, and at that point your mileage may vary. Feel free to certify and share your own success stories...and stay tuned as we will definitely increase these boundaries/guidelines as we complete further tuning and testing.]
According to a recent post in the official blog of Live Mesh, the following is a quick summary of the
I'm using the P2P functionality to sync my wife's pictures from her photography business, it's about 50GB of files. Performance is dreadfuly slow (click on the folder, go make a sandwich, come back) but aside from the slowness it functions just as expected. Hopefully as the beta goes on they'll find a way to speed it up, but even so it is encouraging to see that even in Live Mesh's early stage it still at least works exactly as expected.
Why Live Mesh can not be entirely written in C#?
Why MOE Monitor And Mesh Operating Environments are written in c++ and rest of application is wrriten in c#?
Is because of performance? Or better integration with the operating system??
And in the future we can customize the many settings of Live Mesh have pre configured?
Sorry for the belated reply. The 100 number is actually for the number of devices you can claim in your own mesh, not device types. But yes, we expect to have a wide range of devices interacting Live Mesh, and we’ll have more to say at PDC about how 3rd party developers can have their devices integrate with Live Mesh. You might want to take a look at https://sessions.microsoftpdc.com/public/sessions.aspx
We use managed code extensively in both our client and services. There are some places where native code has to be used, though – for example, in writing integration with the Windows Explorer shell or the display driver integration for Live Remote Desktop. As for customized settings, we’re always looking at new features that customers would appreciate, so please add specific suggestions to the forums' Wish List: http://forums.community.microsoft.com/en/LiveMesh/thread/dd382356-bea0-490d-bfbd-1260224f3846