- Authors of these tools are greedy, very seldom you can get such a tool for free.
- They all trying to use their own channels/services, so you have to have the same software on both ends. And their 'protocols' are not open.
- All services are hard-coded and not extendable.
- They often have poor platform support (e.g. only .NET CF 2.0 & MSBT-stack).
This is the right time for Karapet. Karapet is a mobile services platform, which provides among other things a service registry/directory. It's very scalable and has very little overhead. The core system is lightweight and fast.
To support wide range of Windows Mobile devices, it is build on top of the .NET CF 1.0. It will support following networking services: Bluetooth, IrDA, Wi-Fi and GSM/GPRS.
So, today I got the idea that Karapet concept is something very similar I've already seen in OSGi, moreover in it's .NET CF implementation attempt - Physalis. So, let's go for Physalis and see whether we can reuse something from it to complete the Karapet concept and core.
Another idea is that interface between separate Karapet-enabled devices should be universal for .NET and Java platforms.