Finally a bright idea

Carrying about recent domestic problems I was quiet uninvolved in the development process. If not this mail from one guy yesterday... He asks if he could use Keep Bluechattin' for chatting between two devices via a dedicated channel, thus using a self-created service. This is something I was planning for Karapet and what was not thought for Keep Bluechattin'. Well, at this moment there are dozen of proprietary Bluetooth chat tools which provide this, and even more of them to come. What's the problem with all of them, why none is getting wide acceptance on the market? There are some reasons:

1. Authors of these tools are greedy, very seldom you can get such a tool for free.
   
2. 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.
3. All services are hard-coded and not extendable.
4. They often have poor platform support (e.g. only .NET CF 2.0 & MSBT-stack).

So, there is an emerging market. We are so far and there hundreds of gadgets which support (more or less) either .NET CF or MIDP platform and have Bluetooth/IrDA/Wi-Fi interfaces.

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.