Getting a webhosting service
-
So our student technical group has finally decided to put of our own
website. We have developed it in-house so we want to handle the webhosting
as well, so...
Sunday, July 20, 2008
Busy with EXAMS!!!!
Stuck with prep for multiple exams here.. CCNA and then GRE on 28th July.. and what not..so wont be able to post much this week or two.. Hope my GRE goes well..Wish me luck guys!
Tuesday, July 15, 2008
Virtualization Ahoy!!.
Looking at a lot of info about Virtualization, and especially Microsoft Viridian, I see there are various twists and turns to the whole issue..
PROS..
Same Hardware but multiple software roles.. Imagine Print Server, File Server, RADIUS Server etc all on the same machine but on different OSes.. So any admin repair to the File Server that needs a re-start or suspension of the service wont affect the other services.
CONS..
At the same time, the hardware proves to be a single point of failure. what if the parent OS goes down??
PROS..
Same Hardware but multiple software roles.. Imagine Print Server, File Server, RADIUS Server etc all on the same machine but on different OSes.. So any admin repair to the File Server that needs a re-start or suspension of the service wont affect the other services.
CONS..
At the same time, the hardware proves to be a single point of failure. what if the parent OS goes down??
Monday, July 07, 2008
Singularity - Series III : Look into Contract Based Channels(CBCs)
CBCs - Contract Based Channels can be thought of as Pipes in the conventional OS analogy. CBCs are used for communication between SIPs (Software Isolated Processes).
A CBC is bi-directional and both end points are predefined in terms of functionality, working as an in-order message queue.. The bi-directional CBC's two ends are called as Import End (Imp) and Export End(Exp). The CBC is managed by a predefined protocol that is established by the two communicating SIPs.
Thus the 'Contract' in Contract Based Channel defines the arguments and the protocol that will be used during the communication. It also specifies that the protocol applied to one end i.e. either the Imp End or the Export End will not the inter-changeable.
By the details in the research papers, one can confer that the CBSs are owned by exactly two threads.. that is, one end of the CBC is controlled by one thread exclusively and other end by the other and cant be shared by any other thread of any other SIP. This will force the designers to re-think how multiple threads will communicate with each other. There might be a hypothetical situation where say more than 2 threads need to work on the same set of data, in that case maybe there is some mechnanism for chaining the CBCs.
A CBC is bi-directional and both end points are predefined in terms of functionality, working as an in-order message queue.. The bi-directional CBC's two ends are called as Import End (Imp) and Export End(Exp). The CBC is managed by a predefined protocol that is established by the two communicating SIPs.
Thus the 'Contract' in Contract Based Channel defines the arguments and the protocol that will be used during the communication. It also specifies that the protocol applied to one end i.e. either the Imp End or the Export End will not the inter-changeable.
By the details in the research papers, one can confer that the CBSs are owned by exactly two threads.. that is, one end of the CBC is controlled by one thread exclusively and other end by the other and cant be shared by any other thread of any other SIP. This will force the designers to re-think how multiple threads will communicate with each other. There might be a hypothetical situation where say more than 2 threads need to work on the same set of data, in that case maybe there is some mechnanism for chaining the CBCs.
Subscribe to:
Posts (Atom)
Posts
