Connect ChatEngine.Global

When a user initializes ChatEngine, the client first tries to perform a connection handshake. A series of four ChatEngine.request()s are made in order to connect the User to the default set of ChatEngine channels. These channels are generated based on the ChatEngine.global and the User's uuid strings.

Each request made to the PubNub ChatEngine Function controller sets up ACLs for either the channels or channelGroups array. Granting either read and/or write access to an array of channels. Effectively, these requests make up basic ChatEngine user authorization.

HTTP method	controller*	read	write	channels	channelGroups	authKeys	ttl [sec]
`POST`	`bootstrap`	`true`	`true`	[`global`, `global-pnpres`, `global#chat#public.`, `global#user#UUID#me.`, `global#user#UUID#read.`, `global#user#UUID#write.`]		[`request.body.authKey`]	`request.body.ttl` or `10800`
`POST`	`user_read`	`true`	`false`	`global#user#UUID#read.*`			`request.body.ttl` or `10800`
`POST`	`user_write`	`false`	`true`	`global#user#UUID#write.*`			`request.body.ttl` or `10800`
`POST`	`group`	`true`			[`global#UUID#rooms`, `global#UUID#rooms-pnpres`, `global#UUID#system`, `global#UUID#system-pnpres`, `global#UUID#custom`, `global#UUID#custom-pnpres`]	[`request.body.authKey`]	`request.body.ttl` or `10800`

* The controller field is used to properly route grant requests within the PubNub ChatEngine Function
If field left blank, argument was not used with pubnub.grant()function.

Once all of the above requests have been made, ChatEngine.global waits for a $.connected Event to be emitted, signaling a successful ChatEngine connection to the default global Chats .