 			this.secure = secure;
 			_responseTimer = new Timer( 0.0, 1 );
 			_responseTimer.addEventListener( TimerEvent.TIMER_COMPLETE, processResponse );
-		}
-
-		/**
+			
+			// Default values for super class
+			port = XMPPBOSHConnection.HTTP_PORT;
+		}
+
+		/**
+		 * The first request from the client to the connection manager requests a new session.
+		 *
+		 * <p>The <strong>body</strong> element of the first request SHOULD possess
+		 * the following attributes (they SHOULD NOT be included in any other requests
+		 * except as specified under Adding Streams To A Session):</p>
+		 *
+		 * <ul>
+		 * <li>'to' -- This attribute specifies the target domain of the first stream.</li>
+		 * <li>'xml:lang' -- This attribute (as defined in Section 2.12 of XML 1.0 [17])
+		 *   specifies the default language of any human-readable XML character data
+		 *   sent or received during the session.</li>
+		 * <li>'ver' -- This attribute specifies the highest version of the BOSH protocol
+		 *   that the client supports. The numbering scheme is "major.minor" (where
+		 *   the minor number MAY be incremented higher than a single digit, so it
+		 *   MUST be treated as a separate integer). Note: The 'ver' attribute should
+		 *   not be confused with the version of any protocol being transported.</li>
+		 * <li>'wait' -- This attribute specifies the longest time (in seconds) that
+		 *   the connection manager is allowed to wait before responding to any request
+		 *   during the session. This enables the client to limit the delay before it
+		 *   discovers any network failure, and to prevent its HTTP/TCP connection
+		 *   from expiring due to inactivity.</li>
+		 * <li>'hold' -- This attribute specifies the maximum number of requests the
+		 *   connection manager is allowed to keep waiting at any one time during the
+		 *   session. If the client is not able to use HTTP Pipelining then this SHOULD
+		 *   be set to "1".</li>
+		 * </ul>
+		 *
+		 * <p>Note: Clients that only support Polling Sessions MAY prevent the connection
+		 * manager from waiting by setting 'wait' or 'hold' to "0". However, polling is
+		 * NOT RECOMMENDED since the associated increase in bandwidth consumption and
+		 * the decrease in responsiveness are both typically one or two orders of
+		 * magnitude!</p>
 		 *
 		 * @param	streamType Not used
 		 * @see http://xmpp.org/extensions/xep-0206.html#initiate

			addEventListener( LoginEvent.LOGIN, handleLogin );
		}

		//do nothing, we use polling instead
		override public function sendKeepAlive():void
		{
		}

				active = false;
			}

			// sid is supposed to be only available when creating a new session
			// http://xmpp.org/extensions/xep-0206.html#create
			if ( xmlData.hasOwnProperty("@sid") && !loggedIn )
			{
