This is the first of many technical articles that we will be releasing as we begin our work to bring Hiitch to you as promised in our previous blog postings. We will basically focus on the technology behind building a complete desktop social networking platform like Hiitch and how you can better utilize it for your own purposes without reinventing the wheel. Your suggestions and feedback will be greatly appreciated. You can also write to us about what you would like to know regarding the technologies behind Hiitch.

Hiitch is designed and developed to build a vibrant online community on the desktop. It delivers things of interest such as new people and events to the user by analyzing the user’s profile. It does automatic match making and has an array of features to allow users to interact online (eg. IM, file sharing, photo sharing, community forums, etc) at real time. All these are done securely on the desktop using technologies such as digital signature verification, SSL, data encryption and etc.

Another discussion on Hiitch’s security features can also be found from our previous posting:

How Secure Is Hiitch?

Hiitch is basically (or partially) a client and server networking model. It is not intended to work with web proxies as they post as a big security risk and information leak. All communication done on Hiitch has to be done with direct connections to either the server or the client. A peer to peer model (p2p) for the clients is not used because not all networks allow p2p technologies to work correctly. Some networks hide their computers with transparent proxies to better protect their internal network which result in p2p connection problems. Other disadvantages include the fact that users must have enough know how to configure their home or private network to work with p2p solutions (port forwarding, firewall, DMZ and etc). Often than not a home or private network consists of a group of computers (LAN) and this will require multiple IP addresses not available to most home users. P2P is still a very good networking model and we are still experimenting on how best to combine both p2p models and the more traditional client server models to produce a best of both world solution.

Internally, Hiitch uses a technique similar to remote procedure call (RPC). We will discuss this in more detail in a separate post. All communication data in Hiitch is transmitted using XML. This decision was to allow the client and server to become technology independent and open up possibilities to “just in time” instruction discoveries. So regardless of the programming language used to build the server or client, the only requirement for them (to communicate) is understanding XML. Each instruction(s) send from the client to the server is decrypted (when necessary), parsed and resolved into a set of runtime instructions. These instructions are then checked to see if they are allowed to run. Finally, the instructions are then executed on the server and any results available are returned to the client.

We hope this article will get you excited about Hiitch and the technology behind it. Our hope is that we can build a strong community of experts who are interested and willing to work with us to produce ground breaking social networking technologies for the generations ahead. Join our community today!