‘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.
Generally, this value should be handled by the client. In the case of SparkWeb - for instance we pass a value of 10 to the server. I am assuming the directions are given because JWChat does not supply a default value. Openfire will in this case use the maximum integer which is 2^31-1, so the client can in this case wait for a long time.
The polling interval specified in the blog post relates to how often the client is allowed to poll Openfire. It appears that once again a deficiency in the client forces you to allow unlimited polling on the server which creates a lot of load as the client can basically ask the server if it has any packets an indefinite number of times.