Comparing Technologies 91 When designing an application with
Comparing Technologies 93 Of course, this isn t as powerful as we d want it to be, but it s a start. Next, we could surf the Web to look for pages that have one of the (nowadays almost obligatory) chat links.Although they differ widely in look and feel/implementation,most of them can be boiled down to the following: n Java for fancy interfaces, although some use plain HTML. n A proprietary protocol with a single server (or simply database-backed). n Few predefined rooms. n Few predefined commands. Apart from these chat setups, there are chat applications and networks such as Mirabilis ICQ or the diverse Instant Messaging Systems systems that don t always provide real-time services and generally require additional proprietary client software to be installed on every participating system. However, one system stands out from the list. IRC (Internet Relay Chat) is a widely- known and long-used chat protocol used by many networks, some of which carry hundreds of thousands of users simultaneously.The IRC protocol is text-based a drawback when operating under high load (long string commands generate much more traffic than single binary characters), but this also makes it significantly easier to process. Most current IRC servers support compressed backbone links, which greatly reduce traffic. Although IRC requires special client software on every participating system, we can tweak this requirement to our advantage:Why not provide the client software ourselves server-side, and abstract it by using an HTML interface and allowing each user access to the network through an HTML client? This would give us control over what the user can do (each user is required to use our HTML client).Additionally,we have all the advantages of an existing network system: reliable client software, proven concept,hundreds of tools,etc.We could even allow users to use their own client software an option to be avoided in most cases, however, as we want to create a closed chat network. On a closed network, you know every way that each client can access your network. By limiting the access points to specific setups, you greatly reduce the risk of being attacked. This directly leads to the question, do we need a real protocol such as IRC? Or would it be sufficient to simply use a database-driven protocol, with a remote synchronization feature to provide the requested networking abilities? Questions such as this will arise every time you plan an application, and they ll arise often. Make sure that you ve got all of them covered, and make sure that no questions will arise at a later stage during development. This is the point where you can still address these questions; later on you might be unable to resolve them (and eventually get your project kicked into the trash).A good project is a project without doubts, without uncertainties, without inconsistencies, and without unforeseen eventualities. Make sure that after your planning phase you can assure a stable, fully evaluated situation!
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost PHP MySQL Web Hosting services