Internet Relay Chat, Internet Relay Chat IRC, IRC network.

Internet Relay Chat :

Internet Relay Chat (IRC) is a form of real-time Internet chat or synchronous conferencing. It is mainly designed for group (many-to-many) communication in discussion forums called channels, but also allows one-to-one communication and data transfers via private message.

IRC was created by Jarkko Oikarinen in late August 1988 to replace a program called MUT (MultiUser talk) on a BBS called OuluBox in Finland. Oikarinen found inspiration in a chat system known as Bitnet Relay, which operated on the BITNET.

IRC gained prominence when it was used to report on the Soviet coup attempt of 1991 throughout a media blackout. It was previously used in a similar fashion by Kuwaitis during the Iraqi invasion. Relevant logs are available from ibiblio archive.

IRC client software is available for virtually every PC platform.

Technical information :

IRC is an open protocol that uses TCP and optionally SSL. An IRC server can connect to other IRC servers to expand the IRC network. Users access IRC networks by connecting a client to a server. There are many client and server implementations, such as mIRC and the Bahamut IRCd. Most IRC servers do not require users to log in, but a user will have to set a nickname before being connected.

IRC was originally a plain text, although later extended protocol which on request was assigned port 194/TCP[1] by IANA, but de facto has always been running on 6667/TCP and nearby port numbers to avoid having to run the IRCd software with root privileges.

It is possible (though quite inconvenient) to use IRC via a basic byte-stream client such as netcat or telnet. The protocol does not originally provide any support for non-ASCII characters in text, with the result that many different, incompatible character encodings (such as ISO 8859-1 and UTF-8) are used.

Because most IRC implementations use an acyclic graph as their connection model, there is no redundancy, and outage of a server or a link can cause a netsplit.

Hotel Website in Internet is considered by many of the world's leading travel companies to be the best in its class.The most comprehensive and consistent coverage available of each hotel in its Hotel site by creating high quality, web-friendly, 360° virtual tours and large format still images of each amenity, facility, and room type offered by each hotel.

Anything in IT.com: Find the rate about Logitech G11 Gaming Keyboard coverage, unbiased reviews, exclusive
Video footage and buying guides from www.anythinginit.com.
Visit: Logitech G11 Gaming Keyboard

Internet Online Resources :

Hotels in Canton Georgia : Business travelers will appreciate the convenience of free high-speed Internet access in all rooms of Hotel Comfort Inn Canton, Georgia addition to standard amenities.

Hotel Inn Berkeley CA: The Inn at University is located between Spectular San Francisco and magnificent world famous Napa Wine Country.

Kissimmee Hotel Florida : The Enchanted Hotel is located 3 miles from the Walt Disney World Land Theme Parks and offers easy access to all Central Florida attractions.

Travel Douglas GA : Fountain Inn And Suites near by famous attraction is Fountain Club,Jon’s Sports Park and Wild Adventures Theme Park.

Williamsport PA Hotel : KMD Hospitality Management, LLC is a growth oriented, hospitality management company. However, philosophically KMD Hospitality Management, LLC differs from most hotel management companies.

City Tampa Hotel : The La Quinta Inn Tampa South has spacious rooms with plenty of amenities, including free high-speed Internet.

Evolution :

All client-to-server IRC protocols in use today are descended from the protocol implemented in the irc2.8 version of the IRC2server, and documented in RFC 1459. Since RFC 1459 was published, the new features in the irc2.10 implementation led to the publication of several revised protocol documents; RFC 2810, RFC 2811, RFC 2812 and RFC 2813, however these protocol changes have not been widely adopted among other implementations. IRC 2.11 is most widely used on the IRCnet network. The IRC protocol was extended by Microsoft in 1998 via its IRCX protocol that solves many of the traditional problems that legacy IRC networks faced, along with some features that most users felt were 'ahead of its time'. Although many specifications on the IRC protocol have been published, there is no official specification, as the protocol remains dynamic. Virtually no clients and very few servers rely strictly on the above RFCs as a reference.

While the client-to-server protocols are at least functionally similar, server-to-server protocols differ widely (TS5, P10, and ND/CD are several widely used and incompatible server protocols), making it very difficult to "link" two separate implementations of the IRC server. Some "bridge" servers do exist, to allow linking of, for example, 2.10 servers to TS5 servers, but these are often accompanied with restrictions of which parts of each protocol may be used, and are not widely deployed.

In its first incarnations, IRC did not have many features that are taken for granted today, such as named channels and channel operators. Channels were numbered -- channel 4 and channel 57, for example -- and the channel topic described the kind of conversation that took place in the channel. One holdover of this is that joining channel 0 causes a client to leave all the channels it is presently on: "CHANNEL 0" being the original command to leave the current channel.

The first major change to IRC, in version 2.5, was to add named channels -- "+channels". "+channels" were later replaced with "#channels" in version 2.7, numeric channels were removed entirely and channel bans (mode +b) were implemented. irc2.8 added "&channels" (those that exist only on the current server, rather than the entire network) and "!channels" (those that are theoretically safe from suffering from the many ways that a user could exploit a channel by "riding a netsplit"), and is the baseline release from which nearly all current implementations are derived.
Significant releases based on 2.8 include:

· 2.8.21+CS, developed by Comstud

· 2.8+th, Taner's patchset, which later became

· ircd-hybrid, originally developed by Jon Lusky (Rodder) and Diane Bruce (Dianora) as 2.8/hybrid, later joined by a large development team.

· 2.9, 2.10, 2.11, ... continue the development of the original codebase, mainly for use on the IRCnet network. This development line produced the 4 IRC RFCs released after RFC 1459, which document this server protocol exclusively.
2.8.21+CS and ircd-hybrid continue to be used on EFnet, with ircd-ratbox (an offshoot of ircd-hybrid) as of 2004 being the most popular.

Undernet's IRC server, ircu, is one of the few servers not descended from irc2.8 that are based on the original ircd; it was forked from the irc2.7 codebase.

Many modern IRC servers have been coded from scratch, such as csircd (also from Comstud), ConferenceRoom, Microsoft Exchange Chat Service, InspIRCd, and IRCPlus/IRCXPro. With each new IRCd, a slightly different version of the IRC protocol is used, and many IRC clients and bots are forced to compromise on features or vary their implementation based on the server to which they are connected. These are often implemented for the purpose of improving usability, security, separation of powers, or ease of integration with services. Possibly one of the most common and visible differences is the inclusion or exclusion of the half-op channel operator status (which is not a requirement of the RFCs).

Trademark Attorneye | Customized Wedding Cards | Senior Citizen Jobs | Buy Software India |