text:
Network Working Group C. Kalt Request for Comments: 2813 April 2000 Updates: 1459 Category: Informational
Internet Relay Chat: Server Protocol
Status of this Memo
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved.
While based on the client-server model, the IRC (Internet Relay Chat) protocol allows servers to connect to each other effectively forming a network.
This document defines the protocol used by servers to talk to each other. It was originally a superset of the client protocol but has evolved differently.
First formally documented in May 1993 as part of RFC 1459 [IRC], most of the changes brought since then can be found in this document as development was focused on making the protocol scale better. Better scalability has allowed existing world-wide networks to keep growing and reach sizes which defy the old specification.
Kalt Informational [Page 1] RFC 2813 Internet Relay Chat: Server Protocol April 2000
Table of Contents
- Introduction ……………………………………….. 3
- Global database …………………………………….. 3 2.1 Servers ………………………………………… 3 2.2 Clients ………………………………………… 4 2.2.1 Users ……………………………………… 4 2.2.2 Services …………………………………… 4 2.3 Channels ……………………………………….. 4
- The IRC Server Specification …………………………. 5 3.1 Overview ……………………………………….. 5 3.2 Character codes …………………………………. 5 3.3 Messages ……………………………………….. 5 3.3.1 Message format in Augmented BNF ………………. 6 3.4 Numeric replies …………………………………. 7
- Message Details …………………………………….. 7 4.1 Connection Registration ………………………….. 8 4.1.1 Password message ……………………………. 8 4.1.2 Server message ……………………………… 9 4.1.3 Nick ………………………………………. 10 4.1.4 Service message …………………………….. 11 4.1.5 Quit ………………………………………. 12 4.1.6 Server quit message …………………………. 13 4.2 Channel operations ………………………………. 14 4.2.1 Join message ……………………………….. 14 4.2.2 Njoin message ………………………………. 15 4.2.3 Mode message ……………………………….. 16
- Implementation details ……………………………… 16 5.1 Connection 'Liveness' ……………………………. 16 5.2 Accepting a client to server connection ……………. 16 5.2.1 Users ……………………………………… 16 5.2.2 Services …………………………………… 17 5.3 Establishing a server-server connection. …………… 17 5.3.1 Link options ……………………………….. 17 184.108.40.206 Compressed server to server links ………… 18 22.214.171.124 Anti abuse protections ………………….. 18 5.3.2 State information exchange when connecting …….. 18 5.4 Terminating server-client connections ……………… 19 5.5 Terminating server-server connections ……………… 19 5.6 Tracking nickname changes ………………………… 19 5.7 Tracking recently used nicknames ………………….. 20 5.8 Flood control of clients …………………………. 20 5.9 Non-blocking lookups …………………………….. 21 5.9.1 Hostname (DNS) lookups ………………………. 21 5.9.2 Username (Ident) lookups …………………….. 21
- Current problems ……………………………………. 21 6.1 Scalability …………………………………….. 21 6.2 Labels …………………………………………. 22
Kalt Informational [Page 2] RFC 2813 Internet Relay Chat: Server Protocol April 2000
6.2.1 Nicknames ......................................... 22
6.2.2 Channels .......................................... 22
6.2.3 Servers ........................................... 22
6.3 Algorithms ............................................. 22
7. Security Considerations ……………………………… 23 7.1 Authentication ………………………………….. 23 7.2 Integrity ………………………………………. 23 8. Current support and availability ……………………… 24 9. Acknowledgements ……………………………………. 24 10. References ………………………………………… 24 11. Author's Address …………………………………… 25 12. Full Copyright Statement …………………………….. 26
This document is intended for people working on implementing an IRC server but will also be useful to anyone implementing an IRC service.
Servers provide the three basic services required for realtime conferencing defined by the "Internet Relay Chat: Architecture" [IRC-ARCH]: client locator (via the client protocol [IRC-CLIENT]), message relaying (via the server protocol defined in this document) and channel hosting and management (following specific rules [IRC- CHAN]).
Global database
Although the IRC Protocol defines a fairly distributed model, each server maintains a "global state database" about the whole IRC network. This database is, in theory, identical on all servers.
2.1 Servers
Servers are uniquely identified by their name which has a maximum length of sixty three (63) characters. See the protocol grammar rules (section 3.3.1) for what may and may not be used in a server name.
Each server is typically known by all other servers, however it is possible to define a "hostmask" to group servers together according to their name. Inside the hostmasked area, all the servers have a name which matches the hostmask, and any other server with a name matching the hostmask SHALL NOT be connected to the IRC network outside the hostmasked area. Servers which are outside the area have no knowledge of the individual servers present inside the area, instead they are presented with a virtual server which has the hostmask for name.
Kalt Informational [Page 3] RFC 2813 Internet Relay Chat: Server Protocol April 2000
2.2 Clients
For each client, all servers MUST have the following information: a netwide unique identifier (whose format depends on the type of client) and the server to which the client is connected.
2.2.1 Users
Each user is distinguished from other users by a unique nickname having a maximum length of nine (9) characters. See the protocol grammar rules (section 3.3.1) for what may and may not be used in a nickname. In addition to the nickname, all servers MUST have the following information about all users: the name of the host that the user is running on, the username of the user on that host, and the server to which the client is connected.
2.2.2 Services
Each service is distinguished from other services by a service name composed of a nickname and a server name. The nickname has a maximum length of nine (9) characters. See the protocol grammar rules (section 3.3.1) for what may and may not be used in a nickname. The server name used to compose the service name is the name of the server to which the service is connected. In addition to this service name all servers MUST know the service type.
Services differ from users by the format of their identifier, but more importantly services and users don't have the same type of access to the server: services can request part or all of the global state information that a server maintains, but have a more restricted set of commands available to them (See "IRC Client Protocol" [IRC- CLIENT] for details on which) and are not allowed to join channels. Finally services are not usually subject to the "Flood control" mechanism described in section 5.8.
2.3 Channels
Alike services, channels have a scope [IRC-CHAN] and are not necessarily known to all servers. When a channel existence is known to a server, the server MUST keep track of the channel members, as well as the channel modes.
Kalt Informational [Page 4] RFC 2813 Internet Relay Chat: Server Protocol April 2000
- The IRC Server Specification
3.1 Overview
The protocol as described herein is for use with server to server connections. For client to server connections, see the IRC Client Protocol specification.
There are, however, more restrictions on client connections (which are considered to be untrustworthy) than on server connections.
3.2 Character codes
No specific character set is specified. The protocol is based on a a set of codes which are composed of eight (8) bits, making up an octet. Each message may be composed of any number of these octets; however, some octet values are used for control codes which act as message delimiters.
Regardless of being an 8-bit protocol, the delimiters and keywords are such that protocol is mostly usable from US-ASCII terminal and a telnet connection.
Because of IRC's Scandinavian origin, the characters {}|^ are considered to be the lower case equivalents of the characters []\~, respectively. This is a critical issue when determining the equivalence of two nicknames, or channel names.
3.3 Messages
Servers and clients send each other messages which may or may not generate a reply. Most communication between servers do not generate any reply, as servers mostly perform routing tasks for the clients.
Each IRC message may consist of up to three main parts: the prefix (OPTIONAL), the command, and the command parameters (maximum of fifteen (15)). The prefix, command, and all parameters are separated by one ASCII space character (0x20) each.
The presence of a prefix is indicated with a single leading ASCII colon character (':', 0x3b), which MUST be the first character of the message itself. There MUST be NO gap (whitespace) between the colon and the prefix. The prefix is used by servers to indicate the true origin of the message. If the prefix is missing from the message, it is assumed to have originated from the connection from which it was received. Clients SHOULD not use a prefix when sending a message from themselves; if they use one, the only valid prefix is the registered nickname associated with the client.
Kalt Informational [Page 5] RFC 2813 Internet Relay Chat: Server Protocol April 2000
When a server receives a message, it MUST identify its source using the (eventually assumed) prefix. If the prefix cannot be found in the server's internal database, it MUST be discarded, and if the prefix indicates the message comes from an (unknown) server, the link from which the message was received MUST be dropped. Dropping a link in such circumstances is a little excessive but necessary to maintain the integrity of the network and to prevent future problems. Another common error condition is that the prefix found in the server's internal database identifies a different source (typically a source registered from a different link than from which the message arrived). If the message was received from a server link and the prefix identifies a client, a KILL message MUST be issued for the client and sent to all servers. In other cases, the link from which the message arrived SHOULD be dropped for clients, and MUST be dropped for servers. In all cases, the message MUST be discarded.
The command MUST either be a valid IRC command or a three (3) digit number represented in ASCII text.
IRC messages are always lines of characters terminated with a CR-LF (Carriage Return - Line Feed) pair, and these messages SHALL NOT exceed 512 characters in length, counting all characters including the trailing CR-LF. Thus, there are 510 characters maximum allowed for the command and its parameters. There is no provision for continuation message lines. See section 5 for more details about current implementations.
3.3.1 Message format in Augmented BNF
The protocol messages must be extracted from the contiguous stream of octets. The current solution is to designate two characters, CR and LF, as message separators. Empty messages are silently ignored, which permits use of the sequence CR-LF between messages without extra problems.
The extracted message is parsed into the components
The Augmented BNF representation for this is found in "IRC Client Protocol" [IRC-CLIENT].
The extended prefix (["!" user "@" host ]) MUST NOT be used in server to server communications and is only intended for server to client messages in order to provide clients with more useful information about who a message is from without the need for additional queries.
Kalt Informational [Page 6] RFC 2813 Internet Relay Chat: Server Protocol April 2000
3.4 Numeric replies
Most of the messages sent to the server generate a reply of some sort. The most common reply is the numeric reply, used for both errors and normal replies. The numeric reply MUST be sent as one message consisting of the sender prefix, the three digit numeric, and the target of the reply. A numeric reply is not allowed to originate from a client; any such messages received by a server are silently dropped. In all other respects, a numeric reply is just like a normal message, except that the keyword is made up of 3 numeric digits rather than a string of letters. A list of different replies is supplied in "IRC Client Protocol" [IRC-CLIENT].
Message Details
All the messages recognized by the IRC server and client are described in the IRC Client Protocol specification.
Where the reply ERR_NOSUCHSERVER is returned, it means that the target of the message could not be found. The server MUST NOT send any other replies after this error for that command.
The server to which a client is connected is required to parse the complete message, returning any appropriate errors. If the server encounters a fatal error while parsing a message, an error MUST be sent back to the client and the parsing terminated. A fatal error may follow from incorrect command, a destination which is otherwise unknown to the server (server, client or channel names fit this category), not enough parameters or incorrect privileges.
If a full set of parameters is presented, then each MUST be checked for validity and appropriate responses sent back to the client. In the case of messages which use parameter lists using the comma as an item separator, a reply MUST be sent for each item.
In the examples below, some messages appear using the full format:
:Name COMMAND parameter list
Such examples represent a message from "Name" in transit between servers, where it is essential to include the name of the original sender of the message so remote servers may send back a reply along the correct path.
The message details for client to server communication are described in the "IRC Client Protocol" [IRC-CLIENT]. Some sections in the following pages apply to some of these messages, they are additions to the message specifications which are only relevant to server to
Kalt Informational [Page 7] RFC 2813 Internet Relay Chat: Server Protocol April 2000
server communication, or to the server implementation. The messages which are introduced here are only used for server to server communication.
4.1 Connection Registration
The commands described here are used to register a connection with another IRC server.
4.1.1 Password message
Command: PASS
The PASS command is used to set a 'connection password'. The password MUST be set before any attempt to register the connection is made. Currently this means that servers MUST send a PASS command before any SERVER command. Only one (1) PASS command SHALL be accepted from a connection.
The last three (3) parameters MUST be ignored if received from a client (e.g. a user or a service). They are only relevant when received from a server.
Finally, the last parameter,
Kalt Informational [Page 8] RFC 2813 Internet Relay Chat: Server Protocol April 2000
"P"). See sections 188.8.131.52 (Compressed server to server links) and 126.96.36.199 (Anti abuse protections) respectively for more information on these options.
Numeric Replies:
PASS moresecretpassword 0210010000 IRC|aBgH$ Z
4.1.2 Server message
Command: SERVER
The SERVER command is used to register a new server. A new connection introduces itself as a server to its peer. This message is also used to pass server data over whole net. When a new server is connected to net, information about it MUST be broadcasted to the whole network.
The SERVER message MUST only be accepted from either (a) a connection which is yet to be registered and is attempting to register as a server, or (b) an existing connection to another server, in which case the SERVER message is introducing a new server behind that server.
Most errors that occur with the receipt of a SERVER command result in the connection being terminated by the destination host (target SERVER). Because of the severity of such event, error replies are usually sent using the "ERROR" command rather than a numeric.
Kalt Informational [Page 9] RFC 2813 Internet Relay Chat: Server Protocol April 2000
If a SERVER message is parsed and it attempts to introduce a server which is already known to the receiving server, the connection, from which that message arrived, MUST be closed (following the correct procedures), since a duplicate route to a server has been formed and the acyclic nature of the IRC tree breaks. In some conditions, the connection from which the already known server has registered MAY be closed instead. It should be noted that this kind of error can also be the result of a second running server, problem which cannot be fixed within the protocol and typically requires human intervention. This type of problem is particularly insidious, as it can quite easily result in part of the IRC network to be isolated, with one of the two servers connected to each partition therefore making it impossible for the two parts to unite.
Numeric Replies:
SERVER test.oulu.fi 1 1 :Experimental server ; New server test.oulu.fi introducing itself and attempting to register.
:tolsun.oulu.fi SERVER csd.bu.edu 5 34 :BU Central Server ; Server tolsun.oulu.fi is our uplink for csd.bu.edu which is 5 hops away. The token "34" will be used by tolsun.oulu.fi when introducing new users or services connected to csd.bu.edu.
4.1.3 Nick
Command: NICK
This form of the NICK message MUST NOT be allowed from user connections. However, it MUST be used instead of the NICK/USER pair to notify other servers of new users joining the IRC network.
This message is really the combination of three distinct messages: NICK, USER and MODE [IRC-CLIENT].
Kalt Informational [Page 10] RFC 2813 Internet Relay Chat: Server Protocol April 2000
NICK syrk 5 kalt millennium.stealth.net 34 +i :Christophe Kalt ; New user with nickname "syrk", username "kalt", connected from host "millennium.stealth.net" to server "34" ("csd.bu.edu" according to the previous example).
:krys NICK syrk ; The other form of the NICK message, as defined in "IRC Client Protocol" [IRC-CLIENT] and used between servers: krys changed his nickname to syrk
4.1.4 Service message
Command: SERVICE
The SERVICE command is used to introduce a new service. This form of the SERVICE message SHOULD NOT be allowed from client (unregistered, or registered) connections. However, it MUST be used between servers to notify other servers of new services joining the IRC network.
Kalt Informational [Page 11] RFC 2813 Internet Relay Chat: Server Protocol April 2000
Numeric Replies:
SERVICE email@example.com 9 .fr 0 1 :French Dictionary r" registered on server "9" is being announced to another server. This service will only be available on servers whose name matches ".fr".
4.1.5 Quit
Command: QUIT
Parameters: [
A client session ends with a quit message. The server MUST close the connection to a client which sends a QUIT message. If a "Quit Message" is given, this will be sent instead of the default message, the nickname or service name.
When "netsplit" (See Section 4.1.6) occur, the "Quit Message" is composed of the names of two servers involved, separated by a space. The first name is that of the server which is still connected and the second name is either that of the server which has become disconnected or that of the server to which the leaving client was connected:
<Quit Message> = ":" servername SPACE servername
Because the "Quit Message" has a special meaning for "netsplits",
servers SHOULD NOT allow a client to use a
If, for some other reason, a client connection is closed without the client issuing a QUIT command (e.g. client dies and EOF occurs on socket), the server is REQUIRED to fill in the quit message with some sort of message reflecting the nature of the event which caused it to happen. Typically, this is done by reporting a system specific error.
Numeric Replies:
Kalt Informational [Page 12] RFC 2813 Internet Relay Chat: Server Protocol April 2000
:WiZ QUIT :Gone to have lunch ; Preferred message format.
4.1.6 Server quit message
Command: SQUIT
The SQUIT message has two distinct uses.
The first one (described in "Internet Relay Chat: Client Protocol" [IRC-CLIENT]) allows operators to break a local or remote server link. This form of the message is also eventually used by servers to break a remote server link.
The second use of this message is needed to inform other servers when a "network split" (also known as "netsplit") occurs, in other words to inform other servers about quitting or dead servers. If a server wishes to break the connection to another server it MUST send a SQUIT message to the other server, using the name of the other server as the server parameter, which then closes its connection to the quitting server.
Both of the servers which are on either side of the connection being closed are REQUIRED to send out a SQUIT message (to all its other server connections) for all other servers which are considered to be behind that link.
Similarly, a QUIT message MAY be sent to the other still connected servers on behalf of all clients behind that quitting link. In addition to this, all channel members of a channel which lost a member due to the "split" MUST be sent a QUIT message. Messages to channel members are generated by each client's local server.
If a server connection is terminated prematurely (e.g., the server on the other end of the link died), the server which detects this disconnection is REQUIRED to inform the rest of the network that the connection has closed and fill in the comment field with something appropriate.
When a client is removed as the result of a SQUIT message, the server SHOULD add the nickname to the list of temporarily unavailable nicknames in an attempt to prevent future nickname collisions. See
Kalt Informational [Page 13] RFC 2813 Internet Relay Chat: Server Protocol April 2000
section 5.7 (Tracking recently used nicknames) for more information on this procedure.
Numeric replies:
SQUIT tolsun.oulu.fi :Bad Link ? ; the server link tolson.oulu.fi has been terminated because of "Bad Link".
:Trillian SQUIT cm22.eng.umd.edu :Server out of control ; message from Trillian to disconnect "cm22.eng.umd.edu" from the net because "Server out of control".
4.2 Channel operations
This group of messages is concerned with manipulating channels, their
properties (channel modes), and their contents (typically users). In
implementing these, a number of race conditions are inevitable when
users at opposing ends of a network send commands which will
ultimately clash. It is also REQUIRED that servers keep a nickname
history to ensure that wherever a
4.2.1 Join message
Command: JOIN
The JOIN command is used by client to start listening a specific channel. Whether or not a client is allowed to join a channel is checked only by the local server the client is connected to; all other servers automatically add the user to the channel when the command is received from other servers.
Optionally, the user status (channel modes 'O', 'o', and 'v') on the channel may be appended to the channel name using a control G (^G or ASCII 7) as separator. Such data MUST be ignored if the message wasn't received from a server. This format MUST NOT be sent to clients, it can only be used between servers and SHOULD be avoided.
Kalt Informational [Page 14] RFC 2813 Internet Relay Chat: Server Protocol April 2000
The JOIN command MUST be broadcast to all servers so that each server knows where to find the users who are on the channel. This allows optimal delivery of PRIVMSG and NOTICE messages to the channel.
Numeric Replies:
:WiZ JOIN #Twilight_zone ; JOIN message from WiZ
4.2.2 Njoin message
Command: NJOIN
The NJOIN message is used between servers only. If such a message is received from a client, it MUST be ignored. It is used when two servers connect to each other to exchange the list of channel members for each channel.
Even though the same function can be performed by using a succession of JOIN, this message SHOULD be used instead as it is more efficient. The prefix "@@" indicates that the user is the "channel creator", the character "@" alone indicates a "channel operator", and the character '+' indicates that the user has the voice privilege.
Numeric Replies:
:ircd.stealth.net NJOIN #Twilightzone :@WiZ,+syrk,avalon ; NJOIN message from ircd.stealth.net announcing users joining the #Twilightzone channel: WiZ with channel operator status, syrk with voice privilege and avalon with no privilege.
Kalt Informational [Page 15] RFC 2813 Internet Relay Chat: Server Protocol April 2000
4.2.3 Mode message
The MODE message is a dual-purpose command in IRC. It allows both usernames and channels to have their mode changed.
When parsing MODE messages, it is RECOMMENDED that the entire message be parsed first, and then the changes which resulted passed on.
It is REQUIRED that servers are able to change channel modes so that "channel creator" and "channel operators" may be created.
Implementation details
A the time of writing, the only current implementation of this protocol is the IRC server, version 2.10. Earlier versions may implement some or all of the commands described by this document with NOTICE messages replacing many of the numeric replies. Unfortunately, due to backward compatibility requirements, the implementation of some parts of this document varies with what is laid out. One notable difference is:
* recognition that any LF or CR anywhere in a message marks the end of that message (instead of requiring CR-LF);
The rest of this section deals with issues that are mostly of importance to those who wish to implement a server but some parts also apply directly to clients as well.
5.1 Connection 'Liveness'
To detect when a connection has died or become unresponsive, the server MUST poll each of its connections. The PING command (See "IRC Client Protocol" [IRC-CLIENT]) is used if the server doesn't get a response from its peer in a given amount of time.
If a connection doesn't respond in time, its connection is closed using the appropriate procedures.
5.2 Accepting a client to server connection
5.2.1 Users
When a server successfully registers a new user connection, it is REQUIRED to send to the user unambiguous messages stating: the user identifiers upon which it was registered (RPLWELCOME), the server name and version (RPLYOURHOST), the server birth information (RPLCREATED), available user and channel modes (RPLMYINFO), and it MAY send any introductory messages which may be deemed appropriate.
Kalt Informational [Page 16] RFC 2813 Internet Relay Chat: Server Protocol April 2000
In particular the server SHALL send the current user/service/server count (as per the LUSER reply) and finally the MOTD (if any, as per the MOTD reply).
After dealing with registration, the server MUST then send out to other servers the new user's nickname (NICK message), other information as supplied by itself (USER message) and as the server could discover (from DNS servers). The server MUST NOT send this information out with a pair of NICK and USER messages as defined in "IRC Client Protocol" [IRC-CLIENT], but MUST instead take advantage of the extended NICK message defined in section 4.1.3.
5.2.2 Services
Upon successfully registering a new service connection, the server is subject to the same kind of REQUIREMENTS as for a user. Services being somewhat different, only the following replies are sent: RPLYOURESERVICE, RPLYOURHOST, RPL_MYINFO.
After dealing with this, the server MUST then send out to other servers (SERVICE message) the new service's nickname and other information as supplied by the service (SERVICE message) and as the server could discover (from DNS servers).
5.3 Establishing a server-server connection.
The process of establishing a server-to-server connection is fraught with danger since there are many possible areas where problems can occur - the least of which are race conditions.
After a server has received a connection following by a PASS/SERVER pair which were recognized as being valid, the server SHOULD then reply with its own PASS/SERVER information for that connection as well as all of the other state information it knows about as described below.
When the initiating server receives a PASS/SERVER pair, it too then checks that the server responding is authenticated properly before accepting the connection to be that server.
5.3.1 Link options
Server links are based on a common protocol (defined by this document) but a particular link MAY set specific options using the PASS message (See Section 4.1.1).
Kalt Informational [Page 17] RFC 2813 Internet Relay Chat: Server Protocol April 2000
184.108.40.206 Compressed server to server links
If a server wishes to establish a compressed link with its peer, it MUST set the 'Z' flag in the options parameter to the PASS message. If both servers request compression and both servers are able to initialize the two compressed streams, then the remainder of the communication is to be compressed. If any server fails to initialize the stream, it will send an uncompressed ERROR message to its peer and close the connection.
The data format used for the compression is described by RFC 1950 [ZLIB], RFC 1951 [DEFLATE] and RFC 1952 [GZIP].
126.96.36.199 Anti abuse protections
Most servers implement various kinds of protections against possible abusive behaviours from non trusted parties (typically users). On some networks, such protections are indispensable, on others they are superfluous. To require that all servers implement and enable such features on a particular network, the 'P' flag is used when two servers connect. If this flag is present, it means that the server protections are enabled, and that the server REQUIRES all its server links to enable them as well.
Commonly found protections are described in sections 5.7 (Tracking recently used nicknames) and 5.8 (Flood control of clients).
5.3.2 State information exchange when connecting
The order of state information being exchanged between servers is essential. The REQUIRED order is as follows:
* all known servers;
* all known client information;
* all known channel information.
Information regarding servers is sent via extra SERVER messages, client information with NICK and SERVICE messages and channels with NJOIN/MODE messages.
NOTE: channel topics SHOULD NOT be exchanged here because the TOPIC command overwrites any old topic information, so at best, the two sides of the connection would exchange topics.
Kalt Informational [Page 18] RFC 2813 Internet Relay Chat: Server Protocol April 2000
By passing the state information about servers first, any collisions with servers that already exist occur before nickname collisions caused by a second server introducing a particular nickname. Due to the IRC network only being able to exist as an acyclic graph, it may be possible that the network has already reconnected in another location. In this event, the place where the server collision occurs indicates where the net needs to split.
5.4 Terminating server-client connections
When a client connection unexpectedly closes, a QUIT message is generated on behalf of the client by the server to which the client was connected. No other message is to be generated or used.
5.5 Terminating server-server connections
If a server-server connection is closed, either via a SQUIT command or "natural" causes, the rest of the connected IRC network MUST have its information updated by the server which detected the closure. The terminating server then sends a list of SQUITs (one for each server behind that connection). (See Section 4.1.6 (SQUIT)).
5.6 Tracking nickname changes
All IRC servers are REQUIRED to keep a history of recent nickname changes. This is important to allow the server to have a chance of keeping in touch of things when nick-change race conditions occur with commands manipulating them. Messages which MUST trace nick changes are:
* KILL (the nick being disconnected)
* MODE (+/- o,v on channels)
* KICK (the nick being removed from channel)
No other commands need to check nick changes.
In the above cases, the server is required to first check for the existence of the nickname, then check its history to see who that nick now belongs to (if anyone!). This reduces the chances of race conditions but they can still occur with the server ending up affecting the wrong client. When performing a change trace for an above command it is RECOMMENDED that a time range be given and entries which are too old ignored.
Kalt Informational [Page 19] RFC 2813 Internet Relay Chat: Server Protocol April 2000
For a reasonable history, a server SHOULD be able to keep previous nickname for every client it knows about if they all decided to change. This size is limited by other factors (such as memory, etc).
5.7 Tracking recently used nicknames
This mechanism is commonly known as "Nickname Delay", it has been proven to significantly reduce the number of nickname collisions resulting from "network splits"/reconnections as well as abuse.
In addition of keeping track of nickname changes, servers SHOULD keep track of nicknames which were recently used and were released as the result of a "network split" or a KILL message. These nicknames are then unavailable to the server local clients and cannot be re-used (even though they are not currently in use) for a certain period of time.
The duration for which a nickname remains unavailable SHOULD be set considering many factors among which are the size (user wise) of the IRC network, and the usual duration of "network splits". It SHOULD be uniform on all servers for a given IRC network.
5.8 Flood control of clients
With a large network of interconnected IRC servers, it is quite easy for any single client attached to the network to supply a continuous stream of messages that result in not only flooding the network, but also degrading the level of service provided to others. Rather than require every 'victim' to provide their own protection, flood protection was written into the server and is applied to all clients except services. The current algorithm is as follows:
check to see if client's `message timer' is less than current time (set to be equal if it is);
read any data present from the client;
while the timer is less than ten (10) seconds ahead of the current time, parse any present messages and penalize the client by two (2) seconds for each message;
additional penalties MAY be used for specific commands which generate a lot of traffic across the network.
This in essence means that the client may send one (1) message every two (2) seconds without being adversely affected. Services MAY also be subject to this mechanism.
Kalt Informational [Page 20] RFC 2813 Internet Relay Chat: Server Protocol April 2000
5.9 Non-blocking lookups
In a real-time environment, it is essential that a server process does as little waiting as possible so that all the clients are serviced fairly. Obviously this requires non-blocking IO on all network read/write operations. For normal server connections, this was not difficult, but there are other support operations that may cause the server to block (such as disk reads). Where possible, such activity SHOULD be performed with a short timeout.
5.9.1 Hostname (DNS) lookups
Using the standard resolver libraries from Berkeley and others has meant large delays in some cases where replies have timed out. To avoid this, a separate set of DNS routines were written for the current implementation. Routines were setup for non-blocking IO operations with local cache, and then polled from within the main server IO loop.
5.9.2 Username (Ident) lookups
Although there are numerous ident libraries (implementing the "Identification Protocol" [IDENT]) for use and inclusion into other programs, these caused problems since they operated in a synchronous manner and resulted in frequent delays. Again the solution was to write a set of routines which would cooperate with the rest of the server and work using non-blocking IO.
Current problems
There are a number of recognized problems with this protocol, all of which are hoped to be solved sometime in the near future during its rewrite. Currently, work is underway to find working solutions to these problems.
6.1 Scalability
It is widely recognized that this protocol does not scale sufficiently well when used in a large arena. The main problem comes from the requirement that all servers know about all other servers and clients and that information regarding them be updated as soon as it changes. It is also desirable to keep the number of servers low so that the path length between any two points is kept minimal and the spanning tree as strongly branched as possible.
Kalt Informational [Page 21] RFC 2813 Internet Relay Chat: Server Protocol April 2000
6.2 Labels
The current IRC protocol has 4 types of labels: the nickname, the channel name, the server name and the service name. Each of the four types has its own domain and no duplicates are allowed inside that domain. Currently, it is possible for users to pick the label for any of the first three, resulting in collisions. It is widely recognized that this needs reworking, with a plan for unique names for nicks that don't collide being desirable as well as a solution allowing a cyclic tree.
6.2.1 Nicknames
The idea of the nickname on IRC is very convenient for users to use when talking to each other outside of a channel, but there is only a finite nickname space and being what they are, it's not uncommon for several people to want to use the same nick. If a nickname is chosen by two people using this protocol, either one will not succeed or both will be removed by use of KILL (See Section 3.7.1 of "IRC Client Protocol" [IRC-CLIENT]).
6.2.2 Channels
The current channel layout requires that all servers know about all channels, their inhabitants and properties. Besides not scaling well, the issue of privacy is also a concern. A collision of channels is treated as an inclusive event (people from both nets on channel with common name are considered to be members of it) rather than an exclusive one such as used to solve nickname collisions.
This protocol defines "Safe Channels" which are very unlikely to be the subject of a channel collision. Other channel types are kept for backward compatibility.
6.2.3 Servers
Although the number of servers is usually small relative to the number of users and channels, they too are currently REQUIRED to be known globally, either each one separately or hidden behind a mask.
6.3 Algorithms
In some places within the server code, it has not been possible to avoid N^2 algorithms such as checking the channel list of a set of clients.
Kalt Informational [Page 22] RFC 2813 Internet Relay Chat: Server Protocol April 2000
In current server versions, there are only few database consistency checks, most of the time each server assumes that a neighbouring server is correct. This opens the door to large problems if a connecting server is buggy or otherwise tries to introduce contradictions to the existing net.
Currently, because of the lack of unique internal and global labels, there are a multitude of race conditions that exist. These race conditions generally arise from the problem of it taking time for messages to traverse and effect the IRC network. Even by changing to unique labels, there are problems with channel-related commands being disrupted.
- Security Considerations
7.1 Authentication
Servers only have two means of authenticating incoming connections: plain text password, and DNS lookups. While these methods are weak and widely recognized as unsafe, their combination has proven to be sufficient in the past:
* public networks typically allow user connections with only few
restrictions, without requiring accurate authentication.
* private networks which operate in a controlled environment often
use home-grown authentication mechanisms not available on the
internet: reliable ident servers [IDENT], or other proprietary
The same comments apply to the authentication of IRC Operators.
It should also be noted that while there has been no real demand over the years for stronger authentication, and no real effort to provide better means to safely authenticate users, the current protocol offers enough to be able to easily plug-in external authentication methods based on the information that a client can submit to the server upon connection: nickname, username, password.
7.2 Integrity
Since the PASS and OPER messages of the IRC protocol are sent in clear text, a stream layer encryption mechanism (like "The TLS Protocol" [TLS]) could be used to protect these transactions.
Kalt Informational [Page 23] RFC 2813 Internet Relay Chat: Server Protocol April 2000
Current support and availability
Mailing lists for IRC related discussion: General discussion: firstname.lastname@example.com Protocol development: email@example.com
Software implementations: ftp://ftp.irc.org/irc/server ftp://ftp.funet.fi/pub/unix/irc ftp://coombs.anu.edu.au/pub/irc
Newsgroup: alt.irc
Parts of this document were copied from the RFC 1459 [IRC] which first formally documented the IRC Protocol. It has also benefited from many rounds of review and comments. In particular, the following people have made significant contributions to this document:
Matthew Green, Michael Neumayer, Volker Paulsen, Kurt Roeckx, Vesa Ruokonen, Magnus Tjernstrom, Stefan Zehl.
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[IRC] Oikarinen, J. and D. Reed, "Internet Relay Chat Protocol", RFC 1459, May 1993.
[IRC-ARCH] Kalt, C., "Internet Relay Chat: Architecture", RFC 2810, April 2000.
[IRC-CLIENT] Kalt, C., "Internet Relay Chat: Client Protocol", RFC 2812, April 2000.
[IRC-CHAN] Kalt, C., "Internet Relay Chat: Channel Management", RFC 2811, April 2000.
[ZLIB] Deutsch, P. and J-L. Gailly, "ZLIB Compressed Data Format Specification version 3.3", RFC 1950, May 1996.
Kalt Informational [Page 24] RFC 2813 Internet Relay Chat: Server Protocol April 2000
[DEFLATE] Deutsch, P., "DEFLATE Compressed Data Format Specification version 1.3", RFC 1951, May 1996.
[GZIP] Deutsch, P., "GZIP file format specification version 4.3", RFC 1952, May 1996.
[IDENT] St. Johns, M., "The Identification Protocol", RFC 1413, February 1993.
[TLS] Dierks, T. and C. Allen, "The TLS Protocol", RFC 2246, January 1999.
Author's Address
Christophe Kalt 99 Teaneck Rd, Apt #117 Ridgefield Park, NJ 07660 USA
EMail: firstname.lastname@example.com
Kalt Informational [Page 25] RFC 2813 Internet Relay Chat: Server Protocol April 2000
Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Funding for the RFC Editor function is currently provided by the Internet Society.
Kalt Informational [Page 26]


text:
Java EE 7 Certification Survey - Participants Needed
By Tori Wieldt-Oracle on Oct 10, 2013
Help us define how to serve your training and certification needs for Java EE 7.
Oracle Certification and Server Technologies Curriculum Development are working to build two new Java EE 7 Certification exams and surrounding courses. We are looking to you to help validate our definition of the job roles identified for the Java EE 7 certification.
Our preliminary investigation shows that programmers and developers working with Java EE technology design and create applications using front-end technologies and/or server-side enterprise technologies.
With EE 7, Certified Java Programmers can pursue the Oracle University training courses they need to become either a front-end or server-side developer and then pass a single comprehensive exam that covers all the skills needed for their role.
Earning the new Oracle Certified Expert (OCE) credential distinguishes a Java developer as having the full suite of skills needed in today's marketplace:
- In the Web Application (front-end role), candidates become proficient in building customer-facing applications and designing for the end user.
- In the Enterprise Application (server-side role), candidates master the complexities of designing and building enterprise applications and scalable solutions.
We need your help! We are asking Java practitioners, hiring managers and recruiters to spend 10-15 minutes to complete this survey to help define the scope of the new certification.
NOTE: Your answers will remain anonymous, and you will not be contacted by Oracle as a result of answering this survey.
This survey will remain open through November 30, 2013.

subset: commoncrawl


text:
In this chapter I want to give two instances, in which I have often thought, God favored me with special providences, and perhaps saved my life.
I held a six day's debate with a man (a Campbellite), by the name of W. A. Crum, of Ripley, Mississippi. After the debate closed I had some appointments ahead. (This debate was held at Middleton, Tennessee.) The train that I was to go on was due at 1 o'clock a.m. The man with whom I was staying told me to go to bed and sleep and that he would sit up and call me in good time for the train, so I felt easy and went right off to sleep, and slept until he called me. Strange to say, just about an hour before train time he went to sleep sitting in his chair, and slept on until nearly time for the train. He ran into my room and woke me and told what he had done. I jumped up as quickly as I could and dressed. He gathered my valise and we ran for the depot. When we got in about two hundred yards of the station, the train sailed by and made no stop; so I was left, and very much grieved. I went back to the house and to bed, but not to sleep. Next morning we were out very early, and heard that the train had run past a few miles and had been ditched; several persons killed and many others injured; so I was made to rejoice that the Lord had been so good to me as to preserve me as unworthy as I was, from this dreadful disaster. This I have received as a special providence in my preservation, for a purpose known alone to God.
At another time I had some appointments at Water Valley, Mississippi. I boarded the train at Union City, Tennessee, and ran down to Jackson, Tennessee, where I was to change cars. Our train on the Mobile & Ohio was fifteen minutes late, and the engineer on the Mississippi Central, who knew me and was one of my warmest friends (he was a Baptist in faith), begged the conductor to wait for me. He knew that I was on that train and was due at Water Valley that evening; but the conductor told him he could not, for he had orders to make another connection at Grand Junction, and could not wait. The engineer told him if he would wait for me, he would make the time before he reached Grand Junction; but still he said he could not, so they pulled out and left me. When I got to Jackson and found the train had gone, I was torn to pieces, really I was angry; but I tried to pass away the time as best I could. I said some rough things, and perhaps ugly things to the agent; but he took it all good naturedly and smiled. I presume he was used to being blessed in that way by passengers. In about an hour he called me. I went to see what he wanted and he said, "If you knew what I do, you would be rejoicing instead of frowning." I asked him what it was. He said, "That train you tried so hard to get on has gone through a trestle down here in the edge of Mississippi. The whole trestle fell and all the train went down except the engine, and nearly everybody on the train are killed, even the conductor and flagman. Nearly all the passengers are killed outright. The engine leaped out on the dump, and saved the engineer and fireman.
I burst out crying, I could not keep from it, and said to the agent, "God has again favored me with a special providence, and has preserved my life. Oh, how good the Lord is to me, and I am unworthy of His notice!"
There are many other special providences that have favored me along the journey of life, but we will only mention these two that our readers may see that we have nothing in which we may trust, even for temporal preservation along life's journey, except the sovereign hand of Providence.
I was once traveling through the state of Kentucky and had to change cars at a little place called Nortonville, a very small dismal looking place. I found on my arrival there that I would have a seven-hour wait; so I began walking up and down the platform trying to kill time as best I could. After a while an Irishman, ragged and dirty, came into the depot and took a seat. I noticed he was all the time watching me, and I at last made up my mind that perhaps he was after no good; and so I watched him with a very suspicious eye.
Finally he spoke, as I was passing the door, and said to me, "Come here and sit down. I want to talk to you." I thought, "I am not afraid of you," so I went and sat down. The first thing he did was to reach over and push my hat back. He remarked, "I like your countenance, and feel like I want to talk to you." I said to him, "Talk on then; I will listen to you." He began quoting Scriptures and applying them. I soon found out that he was well versed in the Scriptures and that he understood what they meant, if I did; so I became very much interested; and after he had talked on for some time on that line, he began to tell his experience. He went on to tell what a sinner he felt himself to be, and how he tried to beg the Lord to have mercy on him. At last he said he was down on the railroad not far from that place, and he thought his time had come; he was shoveling dirt and trying to pray, until at last he felt that it was a case made out, there was no mercy for him; yet he felt that God was just, and it was but right that he should be banished from His presence forever. But he said that all at once the trouble left him, light flashed all around him, and the first thing he knew, he was standing between the rails, praising the Lord at the top of his voice, and the other hands all laughing at him; but he said that he did not care for their laughing, he loved the Saviour, and for him.
When he got through I was crying for joy. I loved him and could not help it. I felt like he was my brother, so I told him what I hoped the Lord had done for me; and ere I was aware the train ran up and I had no ticket, and could only run and get on the train, I reached back, after I had got on the step of the car, to shake hands with him, and he kissed my hand before he would turn it loose. I went in and took my seat, was still crying, could not quit, and the conductor came around taking up tickets. When he came to me I told him I had no ticket, but I would pay him the money; and while we were changing the money, he asked me what I was crying about? I tried to waive the subject by telling him that I didn't suppose he would know anything about it if I should tell him; so he went on. But after he had taken all of the tickets, he came back and sat down beside me, and asked me again what I was crying about. I tried to waive it off again by saying that it would be of no interest to him; but he urged me, saying, "I want to know, anyhow." So I told him about the Irishman, and our talk; and before I was done, he was crying, and remarked to me, "I have been wanting to talk to someone on that subject for sometime," and he began and told me his experience. Then I was filled with joy again; and before I reached my destination, he came and handed my money back and told me any time I could strike his train not to get any ticket; "For" he said, "you are the first man I ever talked with that knew my feelings."
I never was permitted to meet either of them any more; but I felt then, and I feel now, that after a while I will meet them both in heaven, if I should ever be permitted to get to that good world; for no man ever taught those two men that lesson. They had never heard it, but they had learned it alone by the revelation of Jesus Christ.
The Primitive or Old School Baptists cling to the doctrines and practices held by Baptist Churches throughout America at the close of the Revolutionary War. This site is dedicated to providing access to our rich heritage, with both historic and contemporary writings.


text:
Greg Travis
Men's Basketball Falls at Youngstown State, 71-50
Flames will open three-game homestand next Saturday vs. Loyola
Flames Close Out 2011 by Hosting Wright State Saturday
UIC will look to capture fifth-straight home win
Flames Collect First Horizon League Win, 63-59 over Detroit
Gary Talton scores career-high 21 points on four three-pointers
Flames Resume Horizon League Play versus Detroit Thursday Night
UIC will look to capture fourth-straight home win
Flames Come up Short at Dayton, 64-57
Barnes, Williams, Talton combine to score 42 points
2011-12: Played in 25 games, staring four contests during the month of November ... Served as UIC's primary back-up point guard ... Averaged 4.0 points, 1.6 rebounds and 2.1 assists per contest ... Posted a 1.2 assist/turnover ratio (53 assists/44 turnovers) ... Scored six or more points nine times, and dished out at least three assists on eight occasions ... Scored a season-high 14 points on 6-of-10 shooting versus Roosevelt (11/16/11) ... Chipped in nine points in back-to-back games against Evansville (11/23/11) and Toledo (11/26/11) ... Scored eight points at Milwaukee (12/3/11) ... Chipped in seven points versus Detroit (12/29/11) ... Scored six points at Valpo (2/14/12) ... Handed out a season-high seven assists and pulled down four rebounds against Evansville.
Prep/Prior to UIC: Four-year letterwinner at Curie High School, where he led the team to four-consecutive Chicago Public League Red-South titles as the starting point guard ... Prep coach was Mike Oliver ... Garnered All-Conference honors as a sophomore, junior and senior ... Was named All-City in each of his final two campaigns ... As a senior, averaged 8.0 points and 7.0 assists per game while shooting 60 percent from the field ... Served as team captain in each of his final two seasons ... Member of the Academic Honor Roll ... On the AAU circuit, played for the "D-Rose All-Stars."
Personal: Full name is Gregory Edward Travis ... Born February 17, 1993 ... Son of Evelyn Mondane ... Intends on majoring in Accounting.


text:
College Hockey:Late Kristo goal lifts North Dakota over Holy Cross
GRAND FORKS, N.D. — Two first period goals were almost enough for Holy Cross, but after holding the lead for the majority of the game, it was toppled by No. 7 North Dakota.
Although they didn't come until late in the game, North Dakota's (12-5-3) goals were enough to claim a 3-2 victory over the Holy Cross Crusaders (10-6-2) in front of 11,587 at Ralph Engelstad Arena.
It wasn't until after they were down by two goals that North Dakota established a way to work into the game, but its continuous shots on the net and a late third period goal by Danny Kristo led the team to its first home sweep of the season.
"We had to work our way into this game," UND coach Dave Hakstol said. "I thought we came out on our toes at the drop of the puck, but tonight we had to work our way into it and that took 10 minutes. We ended up two to nothing to that point in time in order to jolt ourselves into the game."
While it was North Dakota that unveiled the edge Friday night, the Crusaders' momentum was revealed early on Saturday.
After receiving a pass at the bottom of the circle, Brandon Nunn's quick shot on net at 3:23 made it past Clarke Saunders (17 saves) to put Holy Cross on the board first.
"I just think last night we got caught up in where we were playing and who we were playing and tonight we just played and that's a large difference," Holy Cross coach Paul Pearl said. "[Even Zych] had his head up and made a good pass to Brandon [Nunn] and Brandon held it that extra split second and got the puck around Clarke [Saunders] and that was a really good shot."
The Crusaders' persistence continued as a puck battle along the wall allowed Kyle Fletcher's rebound shot to be put in the net by Rob Linsmayer at 13:05 of the first period.
North Dakota was left scoreless until Conner Gaarder got a stick on a pass while skating down the slot and managed to shoot it in past Matt Ginn (34 saves).
Despite picking it up in the second period with 13 additional shots on the net, North Dakota couldn't capitalize on its chances and failed to see the reflection on the scoreboard.
It kept the pressure on the Crusaders' defense in the third period, as Corban Knight's feed to Michael Parks in front of the net allowed Parks to tap in the rebound shot at 4:15 to tie the teams at two.
"They have a bunch of good players and they move the puck well," Pearl said. "They do a good job with that and they did a nice job on that first one they got there to tie it. Their guy got position on our guy out front and it kind of bounced out so that was an unfortunate bounce for us but a great play by them."
It was Danny Kristo who sealed a North Dakota victory at 14:37 on a power play on a snipe through traffic.
"The last one, it comes down to simple things in the game," Hakstol said. "It was a good snap snot from just outside the top of the circle and it ended up being the game-winner. In our minds, that's a pretty power play."
Holy Cross' five penalties in the third period left it short-handed, while North Dakota's offense continued its shots on the net, scoring all three of its goals on the power play.
"I thought we played a pretty good game," Pearl said. "Obviously getting to the third period with a lead is your goal when you're playing teams like this and we did that. Unfortunately, in the third, we took a couple penalties and couldn't kill them off."
While it couldn't kill the penalties, Holy Cross' early start created quick competition right away and kept UND looking for rebounds.
"You've got to give some credit to Holy Cross — they played a lot harder tonight," Kristo said. "They kind of boxed us up a little bit. We weren't getting very many bounces out there and their goalie played extremely well.
"It was just one of those nights where we didn't know if we were going to get the bounces but we just kept on, and kept on and kept pushing and finally got a couple bounces and got the win."
The following is a self-policing forum for discussing views on this story. Comments that are derogatory, make personal attacks, are abusive, or contain profanity or racism will be removed at our discretion. USCHO.com is not responsible for comments posted by users. Please report any inappropriate or offensive comments by clicking the "Flag" link next to that comment in order to alert the moderator.
Please also keep "woofing," taunting, and otherwise unsportsmanlike behavior to a minimum. Your posts will more than likely be deleted, and worse yet, you reflect badly on yourself, your favorite team and your conference.


text:
ōThe Partnership to Promote Healthy Eating and Active Living (The Partnership) was formed in 1999 to address the growing epidemic of chronic diseases related to poor diet and lack of exercise in the United States. The Partnership's mission is to promote healthy eating and physical activity lifestyle behaviors through a public/private partnership grounded on consumer understanding.ö (http://ppheal.org/about_us.html; accessed 8/2/05)
ōThe Partnership is guided by a distinguished Steering Committee with members representing: leading academic institutions including Tufts University and the University of Colorado Health Sciences Center; major food companies including M&M/Mars, Kraft Foods, and Procter & Gamble; and consumer organizations such as The Consumer Federation of America.ö (http://ppheal.org/about_us.html; accessed 8/2/05) The PartnershipÆs Board of Directors includes members from Pepsico, Procter & Gamble, and Goulston & Starrs. (http://ppheal.org/board_of_directors.html; accessed 8/2/05)
America On the Move Sponsors
National Presenting Sponsor
Program Sponsors
Summit on Promoting Healthy Eating and Active Living: Developing a Framework for Progress
An Economic Analysis of Eating and Physical Activity Behaviors: Exploring Effective Strategies to Combat Obesity
Major Donors
Other Contributors
(http://ppheal.org/; accessed 8/2/05)


text:
Hurry! It's Halloween 2012 on Market Street, so grab your camera and go click:
Click to expand
Yes, that's a real car.
Oh here it is, gliding over the MUNI Metro grates of Monkey Station:
Thank you, drive through.
Famous San Francisco street photographer Justin Beck has bounced back from losing his camera on the mean Streets of San Francisco, looks like. He's got another Nikon to work with so that's nice.
Check it, a canary yellow streetcar.
Is this an album cover?
Via JRB – click to expand
Poor pooch. Daijoobu, daijobu. Gambate!
Called 311 for the first time yesterday to see about getting DPW to find a metal grate that's going to stay put atop this hole at Fell and Masonic.
Somehow, I'm 311's "customer" instead of just a Samaritan trying to help San Francisco govmint to its job better.
This thing is more than a foot wide – a touch dangerous, I thought:
Who had the idea to start calling taxpayers customers?
Maybe this is part of the problem?
Anyway, they wanted my phone number.
How 311 having my digits would help DPW I know not…
(Hey is there some button to push so you can talk to the 311 operator right away instead of listening to their canned spiel? I know not. Oh well.)


text:
Whirlpool® Dishwasher with Resource-Efficient Wash System
Get the clean you need without wasting water or energy. Dishwashers with the Resource-efficient wash system clean a full load of dishes using nearly 1/2 the water and energy1. The industry's most energy-efficient dishwashers3 are ENERGY STAR® qualified and even feature an eco-friendly CEE Tier 22 qualification. But being green doesn't mean you have to give up great cleaning. This model features our improved AnyWare™ Plus silverware basket that holds up to 12 more pieces of silverware and is designed to clean better. Placing the silverware basket in the bottom rack, in the door or in the front of the rack will also give you 100% usable rack space.
Dimension Guide
Detailed dimensions of your new appliance with space requirements for the area surrounding it.
Installation Guide
Instructions for unpacking and installing your appliance, including electrical requirements and necessary tools.
Energy Guide
Information about the efficiency of your appliance, including energy consumption and annual costs to operate.
Use & Care Guide
Comprehensive information about your new appliance - from getting started to cleaning and maintenance.
Warranty Information
A complete description of your warranty coverage, and contact information for service and support.
Adobe Reader
These documents require Adobe Reader to view.
You can download the latest version of Adobe Reader for free.
Replacement Parts
To buy replacement parts for your appliance > click here to visit our partner
Accessories You'll Want
Top Features
ENERGY STAR® Qualified
AnyWare™ Plus Silverware Basket
The AnyWare™ Plus silverware basket frees up rack space by easily fitting on the front of the lower rack or in the door to make room for more dishes.
Resource - Efficient Wash System
This dishwasher's resource-efficient wash system cleans a full load of dishes using nearly 1/2 the water and energy1. Whirlpool Brand's improved motor and wash system optimizes cleaning for better cleaning results versus the previous wash system and provides our quietest line of dishwashers ever.
Additional Features
No One Has Fewer Repairs 18 Years in a Row
According to a leading consumer magazine; Whirlpool® dishwashers.
CEE Tier 14 qualified
Select dishwashers exceed federal minimum energy efficiency standard by 15% to earn an eco-friendly CEE Tier 14 qualification. These advanced water and energy savings may qualify for rebates, contact your local utility company for program availability.
Overnight Cycle
The Overnight cycle quietly soaks your dishes with an extended prewash and then runs a Heavy Wash cycle to clean tough soils. This industry-exclusive, 7-hour cycle optimizes water efficiency, without using more energy or disrupting household activities.
Eco Wash Cycle
Our most efficient dishwasher cycle helps minimize energy and water usage while cleaning dishes5. This eco-friendly cycle delivers great cleaning performance and is the perfect cycle for cleaning lightly to moderately soiled dishes.
Triple Filtration System
Resource efficient dishwashers feature a triple filtration system to remove food particles and other soils. This highly effective filtration system helps the wash system provide outstanding cleaning while using less water and energy.
1-Hour Wash Cycle
The 1-Hour Wash cycle cleans dishes in half the time.
Eco Dry Option
The industry-exclusive Eco Dry option is the most efficient drying option on our dishwashers. Perfect for those who want to save energy, its shorter heating time uses 70% less energy compared to using Heated Dry6.
NSF Certified Sani Rinse Option
Make sure your dishes are reliably clean with the NSF Certified Sani Rinse option. Using a high temperature rinse, this option eliminates 99.999% of food soil bacteria, as certified by NSF International.
High Temperature Wash System
Choose this option when additional cleaning of items like baby bottles glassware or dishes is required.
2-4-8 Hour Delay Wash Option
Washes dishes according to your schedule. Lets you delay washing for up to 8 hours during off-peak hours when utility rates may be lower.
Control Lock
Disables buttons on the control panel to help prevent unwanted starting or stopping the dishwasher.
Our Quietest Line Of Dishwashers Ever
Our quietest line of dishwashers ever offers many levels of quiet operation. Equipped with our Quiet Partner™ sound packages and sound-reducing insulation, these models minimize noise, so you can run the dishwasher without it interfering with your daily routine.
Plastic Cup Shelf
Allows you to stack two levels of coffee mugs or secure delicate glassware during the wash cycle when used as a stemware holder.
Light Item Clips
Light item clips secure lightweight items during the wash cycle and help prevent items from falling out of the basket. They also stop cups and other small containers from flipping over and filling with water.
Tall Tub Design
This model's Tall Tub design allows you to load tall and odd-shaped items in both racks. An additional 3" of interior space compared to standard tub models makes room for extra-large items in the lower rack and plates or sports bottles in the upper rack.
Auto Soil Sensor
The Auto soil sensor optimizes every cycle for reliable cleaning results. This sensor measures water clarity to determine how dirty dishes are, then adjusts the cycle accordingly. This sensor measures the soils in the water and will add extra water and even temperature to ensure clean dishes. It automatically recalibrates the load after every 250 wash cycles for maximum performance.
Quiet Partner™ II Sound Package
Whirlpool brand dishwashers offer many levels of quiet operation with this system of sound reducing insulation.
Configuration and Overview
Cycle and Options
Product Dimensions
- 24 1/2
- 34 1/2
- 23 7/8
Dimensions are for planning purposes only.
For complete information, visit service and support.


text:
Returning starter at one defensive tackle position ? Great work ethic and intensity ? Has played in 35 career games, starting 15 times.
1998:Started every game of the season at defensive tackle ? Led all UMass defensive linemen in tackles with 66, including 38 solo stops ? Had six sacks for 30 yards and nine tackles for loss ? Also had one forced fumble ? Totaled a career-best nine tackles against Georgia Southern in the NCAA championship game ? Made four tackles in NCAA semifinal win at Northwestern State, including a sack ? Had four tackles and a pass breakup in NCAA quarterfinal win over Lehigh ? Made four tackles at McNeese State in the NCAA first round, including one for loss ? Totaled seven tackles in the home game against Connecticut, four solo and one for loss ? Made three tackles against Maine, including a sack for five yards ? Made five tackles at Rhode Island, including a sack for 12 yards ? Had eight tackles against James Madison, including one for loss ? Had two sacks for 10 yards at Richmond ? Made six tackles at Delaware, three for loss, with a sack for two yards and a forced fumble.
1997:Played in all 11 games at defensive tackle, all as a reserve ? Finished with 17 tackles (six solo), including two tackles for loss, one sack and one fumble recovery ? Made three tackles with one tackle for loss against Richmond ? Had three tackles in the victory over Rhode Island ? Recorded a sack in the victory at Buffalo ? Recovered a fumble against Hofstra.
1996:Saw action in nine games ? Recorded three assisted tackles on the year.
1995:Redshirted. Before UMass: Played both defensive tackle and tight end for Joe Ursida at New Brighton High School ? Recorded four sacks, while also averaging 17.7 yards per catch and scoring one touchdown at tight end during his senior season ? First-team All-Western Pennsylvania choice both on offense and defense as a senior ? Honorable Mention All-Western Pennsylvania pick on offense and defense during his junior season ? His high school team won the Western Pennsylvania Interscholastic Athletic League championship game, played in Three Rivers Stadium ? Played tight end in the Pennsylvania-Ohio All-Star game after his senior season ? Member of National Honor Society.
Personal:Full name is Aaron Edward Parker ? Son of Ed and Kathleen Parker ? Father played football at Marshall University ? Born November 11, 1976 in Rochester, Pa. ? Comes from the talent-rich football area in Western Pennsylvania that produced such greats as Joe Namath, Tony Dorsett and Mike Ditka ? Majoring in Exercise Science.
Parker's Career Statistics
Featured Links
More Headlines


text:
Feb 10, 2014 8:10 AM
It's a hot summer afternoon. Where do your thoughts turn when it comes to liquid refreshment? Probably a cool gin and tonic or a frosty beer. But the recipes in Cool Waters: 50 Refreshing, Healthy, Homemade Thirst Quenchers ($12) sound so appealing, they might just turn cocktail hour into "delicious good-for-you-beverage time."
If you've got a product or service that you'd like to promote on Outblush, click here to find out about our advertising opportunities.
Outblush is a blog for girls who love to shop. Our staff digs up the best clothes, home stuff, beauty items, and more. New items are posted every day — bookmark us and check out:


text:
You never know when you are going to witness history in the making. It just happens, and when it does, there is a moment, somewhat akin to enlightenment, when the mere act of watching something unfold before your eyes, becomes a moment of a brand new awareness. That is what happened last night when Allen Toussaint performed at City Winery Napa.
Toussaint, with over 50 years in the music business, is a seasoned professional, to be sure, but to see him perform up close and in the intimate setting curated by the City Winery people, expectations of a good performance are simply blown out of the water. Though my familiarity with his music is limited to just a couple albums, I had a pretty good idea that Napa was in for something special. What I didn't expect, was a nearly capacity crowd, almost all of whom were perched on the edge of their seats, repeatedly alternating between tears and boisterous laughter as Toussaint wove tales of a life lived, good times and bad, and everything in between, while noodling on the piano and slipping into and out of iconic New Orleans-style rhythm and blues tunes. The whole thing was simply effortless, and it was one of the most generous performances I have ever seen. One gentleman in attendance reminisced about how last night's performance reminded him of the fortunate and life-changing occasion when he saw Ella Fitzgerald perform in Copenhagen in 1979. Though I can only imagine what that was like, I do know what I experienced last night, and that was pure magic.
As the evening approached the inevitable end, the crowd was utterly transfixed and hanging on every word and note put out there by Toussaint, he made a request for anyone in the audience who plays piano to join him on stage. A man named Charlie Thompson stood up, slid a chair up against the grand stage of the old opera house, stepped on up, and took his place next to Mr. Toussaint on the piano bench. At this point, the entire crowd was standing and cheering as a mad four-hand boogie-woogie throwdown exploded from the shiny, black Steinway.
City Winery Napa at the Historic Napa Valley Opera House is located at 1030 Main Street, right in the middle of downtown Napa. For more information about upcoming shows, click here. To get social with City Winery Napa visit their Instagram, Facebook, or Twitter pages.


text:
I thought we would be back to civilisation once we got to Port Augusta, but there really wasn't much other than some sheep and a wind farm until we hit the outskirts of Adelaide.
We started our last day on the train with another scrumptious breakfast and pulled into Adelaide just before noon.
Our hotel in Adelaide is just off the eastern end of Rundle Street where there are plenty of cafes and restaurants. We walked to Exchange Specialty Espresso where we grabbed a coffee and a sandwich for a quick lunch. We spent the afternoon exploring Rundle Street. Dinner was at United Latino Cocina where we had Arepas and Ropa Viejo washed down with a margarita. The Arepas were excellent while the Ropa Viejo lived up to its name ????.
Comments Off on Day 8 – Arrival in Adelaide


text:
After the 2008 stock market crash, many stockholders began unloading underperforming or damaged assets from their investment portfolios.
One such financial example is Bank of America, which in 2011 Huffingtonpost.com said "has seen the value of its stock decline by 54 percent since the start of 2011."
"From a fundamental standpoint," noted Gerard Plauche, a chartered financial analyst and partner at Delta Financial Advisors in New Orleans, "We analyze a company to determine the reasons for the downturn in the stock's performance."
Said Plauche: "If it is a short term issue, then it would warrant holding or adding to the position. If not, it should be sold and replaced with a stock that has better potential."
Story by
Mackie Shilstone,
Contributing writer
Does each NFL team -- with an investment portfolio composed of 53 stocks (players on an opening-day roster) with some damaged assets (injured players) -- get caught up in this same asset management philosophy?
An Associated Press story last week led with, "Broken bones. Torn ligaments. Subpar performances. They all combined to sideline some of the NFL's biggest stars a year ago." In the NFL, it's all about performance - today.
One such case is New England Patriots' tight end Rob Gronkowski, who said, " I was rehabbing every day, and it was miserable." The AP story noted that Gronkowski "is still working his way back from a vicious two-year stretch in which he has had four forearm surgeries, a back injury, and torn knee ligaments."
Another notable name on the comeback trail -- a shadow of his standout rookie season two years ago -- is Redskins quarterback Robert Griffin III, who tore his anterior cruciate ligament (ACL) in a Redskins' playoff game. Griffin, up to now, has not been the same since his rookie season.
Saints running back Pierre Thomas did not dress out for the preseason game against the Rams due to an unknown injury.
Thomas' stock value -- based on a snapshot of his injury history and his performance statistics -- will figure into a determination of his ranking on the Saints' chief financial officer's (CFO) balance sheet. In this scenario, Thomas is being viewed as an asset with an associated cost and risk/benefit ratio -- tied to his return on investment.
Sortrac.com notes Thomas is in the final season of a three-year, $6.9 million contract. He missed 12 weeks in 2010 with an ankle injury, missed four weeks with a knee injury in 2012 and missed a playoff game with a chest injury in 2013.
Plauche said "a player has to be an asset to the team, (and) as a stock needs to add value to an overall investment portfolio."
The good news for Thomas is that he returned to practice this week.
Ultimately, a player will use physical fitness to reduce his risk to a "downturn." But, an NFL team, like the Saints, will need fiscal fitness to be able to compete in the market place for high performing stocks (players).
Time will tell as to which players will ultimatly answer the opening bell of the 95th NFL stock exchange on Sept. 4.
Mackie Shilstone, a regular contributor to NOLA.com | The Times-Picayune, has been involved in the wellness sports performance industry for nearly 40 years. He is currently the fitness coach for Serena Williams, has trained numerous other professional athletes and consulted a litany of professional sports franchises. He is St. Charles Parish Hospital's Fitness and Wellness expert. Contact him at mackieshilstone.com.


text:
Below is an exhaustive list of LoadRunner interview questions, covering basic and advanced topics like "What is LoadRunner ?", "What is load testing ?", LoadRunner scripting, LoadRunner functions, LoadRunner result analysis, LoadRunner controller, LoadRunner correlation and other LoadRunner features.
Prepare for interviews by answering these questions to best of your knowledge and experience OR learn from the answers provided by others.
1. What is load testing ? Answer
2. What is LoadRunner ? Answer
3. What is Performance testing ? Answer
4. What is HP Performance Center ? Answer
5. What is Performance Engineering ? Answer
6. What are performance bottlenecks ? Answer
7. Explain the Load testing process ? Answer
8. What are the benefits of using LoadRunner tool ? Answer
9. What are the different types of Analysis Graphs provided by LoadRunner ? Answer
10. What is Remote Agent Dispatcher ? How is it different from LoadRunner Agent ? Answer
11. What are the different tools and options provided by LoadRunner to view a summary of the results after test
execution ? Answer
12. What is Correlation ? Answer
13. What is HP Business Availability Center ? Answer
14. What is the difference between Load Testing and Stress Testing ? Answer
15. What is the difference between Performance Testing and Load testing ? Answer
16. What is the version of the LoadRunner Software you have worked with ? Answer
17. What is SSL ? Answer
18. What is LDAP ? Answer
19. What is scenario ? Answer
20. How to Load a DLL locally Answer
21. How did you plan the Load ? Answer
22. What is Solution Explorer ? Answer
23. How to Load a DLL Globally ? Answer
24. What are the different Vuser Types ? Answer
25. What information does default.cfg contain ? Answer
26. what are Protocols ? Why there are so many protocols ? Answer
27. What is SSH ? What is the difference between SSL and SSH ? Answer
28. What is HTTP ? Answer
29. What is the difference between HTTP and HTTPS ? Answer
30. What is the difference between Business process flow and scenario ? Answer
31. What are the browsers supported by LoadRunner for Click & Script recording ? Answer
32. What are the steps to configure LoadRunner Run-Time Settings and Parameters ? Answer
33. What are the LoadRunner API method used for calling External Functions in DLLs ? Answer
34. What are the LoadRunner XML APIs that you have used ? Explain each of them briefly Answer
35. What would you do if you see an error stating GUI object not found after first iteration ? Answer
36. When you are recording script and you see problems with recording like images are not loaded, only part of the webpage is loaded or popup window does not open, what do you do ? Answer
37. What is ODBC ? Answer
38. What is VuGen ? Answer
39. What is transaction ? Answer
40. What is a controller ? Answer
41. What are Header Files ? Answer
42. What is a Load Generator ? Answer
43. What are parameter types ? Answer
44. What is a Terminal Emulator ? Answer
45. What is Performance analysis ? Answer
46. Why do you create Parameters ? Answer
47. What is Documentation Library ? Answer
48. Explain about XML Parameter Type Answer
49. Explain about Table Parameter Type Answer
50. What are Mailing Service protocols ? Answer
51. Explain about Internal Data Parameter Type Answer
52. What is version control ? What is its importance ? Answer
53. When to enable and disable socket level recording ? Answer
54. What is the difference between action and Transaction ? Answer
55. What is the protocol used for testing SAP applications ? Answer
56. Explain different parameter types supported by LoadRunner ? Answer
57. What is ALM (Application Lifecycle Management Connection) ? Answer
58. Explain about User-Defined Function Parameters with and example Answer
59. What are the steps for importing Parameter data from database ? Answer
60. What is the protocol used for testing IBM Mainframe applications ? Answer
61. what is DNS ? Answer
62. What is RMI ? Answer
63. What is CORBA ? Answer
64. What is DNS Caching ? Answer
65. What is Virtual Users ? Answer
66. How do you encode Passwords ? Answer
67. What is URL ? What are the contents of URL ? Answer
68. What are the protocols you have worked with ? Answer
69. What is the type of encryption supported by LoadRunner ? Answer
70. What is the LoadRunner function to decrypt encrypted text ? Answer
71. What is connection pooling ? What are the advantages of connection pooling ? Answer
72. What is a scenario ? Answer
73. What is Flex Recording Mode ? Answer
74. What is LoadRunner License Utility ? Answer
75. What is the difference between Node Locked and Unlocked license ? Answer
76. What is think time ? Answer
77. What is ideal think time ? Answer
78. How to Work with Version Controlled Scripts in ALM
Projects ? Answer
79. How have you implemented version controlling for LoadRunner scripts ? Answer
80. What is Throughput ? Answer
81. Explain LoadRunner Support for Asynchronous Communication. Answer
82. What are monitors ? Answer
83. How to Query an XML Tree ? Answer
84. What is extended log ? Answer
85. What is report viewer ? Answer
86. What is Rendezvous point ? What is the need for Rendezvous points ? Answer
87. What is scenario wizard ? Answer
88. What is LoadRunner Agent. Answer
89. How to Serialize Scripts with the LoadRunner Serializer ? Answer
90. What is Manual Correlation ? Answer
91. What is lrd_stmt ? Answer
92. What is lrd_fetch ? Answer
93. What is IP Spoofing ? Answer
94. What is Animated Run ? Answer
95. What is lr_debug_message ? Answer
96. What is lr_error_message ? Answer
97. What is lr_output_message ? Answer
98. What is the use of Breakpoints ? Answer
99. What is LoadRunner API function ? Answer
100. What is smart object recognition ? Answer
101. How to use network drive mappings ? Answer
102. What does vuser_end action contain ? Answer
103. What does vuser_init action contain ? Answer
104. What is Elapsed Time in LoadRunner ? Answer
105. How do you debug a LoadRunner script ? Answer
106. What are the components of LoadRunner ? Answer
107. What is Ramp up ? How do you set this ? Answer
108. How to select item from virtual list box ? Answer
109. How did you find database related issues ? Answer
110. Does LoadRunner support IPV6 applications ? Answer
111. What is the significance of "Vuser-init " ? Answer
112. How did you find web server related issues ? Answer
113. How many types of graphs are in LoadRunner ? Answer
114. When do you do load and performance Testing ? Answer
115. What are the protocols supported by LoadRunner ? Which of them have used used during load or performance testing ? Answer
116. Where do you set Iteration for Vuser ? Answer
117. How to write user defined functions in LR ? Answer
118. How many VUsers are required for load testing ? Answer
119. Where do you set automatic correlation options ? Answer
120. Explain the recording modes for web Vuser script. Answer
121. How do you identify the performance bottlenecks ? Please explain step by step. Answer
122. What are the languages used for VuGen Recording and Scripting ? Answer
123. Is it possible to perform functional testing using LoadRunner ? Answer
124. What are the languages supported by VUGen editor ? Answer
125. How do you find out when and where correlation is required ? Answer
126. What are the steps for creating a Vuser Script ? Answer
127. How to set the number of Vusers in LoadRunner ? Answer
128. How to end a nested transaction ? Answer
129. How to enable thumbnail generation in LoadRunner ? Answer
130. What is the advantage of running Vuser as thread ? Answer
131. What are the changes you can make in run-time settings ? Answer
132. What is the LoadRunner start-transaction and its syntax ? Answer
133. What is the difference between load and performance testing ? Answer
134. What is the relation between Response Time and Throughput ? Answer
135. How to divide script into multiple Actions ? What is the advantage of dividing script into multiple actions ? Answer
136. What are the difference between standard log and extended log ? Answer
137. What are the types of check points is available in LoadRunner ? Answer
138. What are the various types of Goals in Goal-Oriented Scenario ? Answer
139. What component of LoadRunner is used to record a Script ? Can the script be created without recording ? If yes, how and have you created any script without recording ? Answer
140. Where should you add a web_reg_save_param function to a script ? Answer
141. Does caching have a negative effect on your load testing results ? Answer
142. What is the difference between Overlay graph and Correlate graph ? Answer
143. What is a function to capture dynamic values in the web Vuser script ? Answer
144. What is the difference between lr_error_message and lr_debug _message ? Answer
145. Which web protocol recording level generates the web_submit_form function ? Answer
146. How Asynchronous Functions Differ from Synchronous Functions in LoadRunner ? Answer
147. when a load test fails and web server, database and Network seem to be working fine, where could be the problem ? Answer
148. If you want to stop execution of a script on error, how do you do that ? Answer
149. What is the importance of ordinance in web_reg_save_param during correlation ? Answer
150. What is the difference between transaction and transaction instance ? Answer
151. What component of LoadRunner would you use to play Back the script in multi user mode ? Answer
152. When to use standard and when to use extended logs ? Answer
153. What are the different types of bottlenecks you have uncovered in the load tests you performed ? Answer
154. Is running Vuser as process more advantageous than running Vuser as thread ? Explain. Answer
155. What is the difference between Process and Thread ? Answer
156. Have you attended any formal trainings for LoadRunner ? Answer
157. What do you know about LoadRunner certification ? Are you preparing for LoadRunner certification ? Answer
158. Explain LoadRunner architecture. Answer
Thanks Lakshmi, for covering most of the LoadRunner interview questions. As always, your contribution has helped our software testing blog visitors.
Other Interesting Articles:
- Test scenarios for Pen
- Software Testing Interview Tips
- Load Testing or Performance testing Transactions
- What are the challenges that you faced in your current/previous job ?
- where do you see yourself in 5 years ?


text:
The 2014 Black Entertainment Television (BET) Honors ceremony was held Saturday night at the Warner Theater in Washington, DC. The purpose of this annual event is to celebrate extraordinary African-American achievement and accomplishment.
The 2014 BET Honorees are Motown Records founder Berry Gordy, legendary R&B singer Aretha Franklin, actor and rapper Ice Cube, artist and photographer Carrie Mae Weems, CEO of American Express Kenneth Chenault, and the great political activist, humanitarian and President of South Africa Nelson Mandela.
Ice Cube received the Entertainment Award for his impressive career in music, film and television. He is currently starring in the movie Ride Along which has generated over $100 million, and has topped the charts for three weeks in a row. Ice Cube's 10th solo album Everythang's Corrupt is scheduled to drop later in the year.
Kenneth Chenault has been the CEO and Chairman of American Express since 2001. Mr. Chenault is the third African-American CEO of a Fortune 500 company, and Ebony Magazine has listed him as a "living pioneer" in the African-American business community.
Carrie Mae Weems is an artist who uses photography, fabric, audio and video to explore and examine African-American culture. Her exhibit "Three Decades of Photography and Video" will be on display through May 14, 2014 at the Guggenheim Museum in New York City.
Every year the BET Honors brings to DC an amazing collection of celebrity and talent. Among the performers and attendees were: Jennifer Hudson, Mariah Carey, Janelle Monae, Ludacris, Smokey Robinson, Fonzworth Bentley, Michael Bivins, Russ Parr, Karen Clark Sheard, Debra Lee, Wolf Blitzer, Ski Johnson, and Wayne Brady who hosted the show. Tamar Braxton also performed, and graced the stage and red carpet wearing Michael Costello Couture.
The 2014 BET Honors will be televised on February 24th. For more information about BET Honors, please visit: www.bet.com/bethonors.


text:
Suzie Lombardo of Statice is a floral and event designer based in Greenville SC. Her love affair with flowers began as a child when she visited her Oma (grandmother) in Germany. Suzie recalls spending hours on that trip with her grandmother in the garden. Germans refer to watering the garden as "garten giessen" which literally means "garden pour". " I've always thought that word made sense, to pour. If you are passionate about something and you wish to see it flourish, you must pour into it. That is what I do with these flowers. I've learned about them, surrounded myself with them, spent countless hours admiring their beauty. I love them, and they have helped me grow this business that I also love. For me... it's about the flowers."
Suzie graduated from Clemson in 2011 with a degree in Horticulture. Her knowledge of plants and the seasonality of flowers helps her come up with the best possible flower options for your wedding. Whether you are in need of simple bridal party flowers or full scale event design, Suzie can help make your wedding vision a reality.
She offers comlimentary consults for wedding florals and event design services. Call today!
Contact us today at 864-450-3754. We are looking forward to designing for you!


text:
UWellness – Be Healthy
More Health Resources at Work
A healthy you is a wonderful thing! You feel great, sleep well, and help maintain a healthy workplace. Whether you're seeking to reduce stress or be physically and mentally fit, check out these resources to be healthy and stay healthy at work.
Disability Accommodations
Do you need accommodations for a medical condition or disability to help you be successful in your job? The Disability Services Office can help you explore reasonable accommodation resources, including assistive equipment, interpreter services, and parking or transportation.
Hall Health Services
Hall Health Center is an on-campus outpatient clinic offering high-quality health care and wellness services to UW employees. Services available include physical therapy, health assessments and physicals, and counseling and therapy for mental health concerns. Hall Health Center accepts most major health insurance plans.
Lactation Stations
While it may be hard to leave your baby when you return to work, you shouldn't have to give up breastfeeding. UW supports breastfeeding moms with a convenient lactation program. Find an onsite lactation station, learn about accessories you may need, and explore other resources for nursing moms.
UW Speech and Hearing Clinic Services
The UW Speech and Hearing Clinic, a teaching outpatient clinic, provides excellent on-campus care at affordable rates. It offers evaluation and treatment services for children and adults with speech, languages, hearing, and related communication needs, including hearing aid testing, fitting, and repair. UW employees also may receive a complimentary hearing screening; space is limited, so reserve your spot in advance.
UW Women's Center
The UW Women's Center offers a safe space and point of contact for students and community members in addressing sensitive issues in their lives, such as depression and eating disorders. It houses a large collection of resources that enable the staff to connect those in need with appropriate services.


text:
The Qatar Masters
Doha Golf Club © Slippy Slappy
The Qatar Masters golf tournament is held annually at the Doha Golf Club as part of the European and Asian PGA tours, attracting golfers and fans from around the world. The competition takes place on the unique and challenging desert-style course designed by Peter Harradine, one of the most acclaimed golf course designers in the world today.
Venue: Doha Golf Club, West Bay
Date: January 2017 TBC
Website: www.qatar-masters.com