powered by Jive Software

Xmpp.httpbind properties

Hi,

Ive found a [post](https://community.igniterealtime.org/docs/DOC-1061) in the jwchat forum suggesting to add several xmpp.httpbind properties to openfire so itll work with jwchat:

xmpp.httpbind.client.idle 3600

xmpp.httpbind.client.requests.max 2

xmpp.httpbind.client.requests.polling 0

xmpp.httpbind.client.requests.wait 60

I understand that the wait and max properties should be set by the client. I also understand the polling property.

Does the idle property allow client not to send httpbind request for 3600 ms and keep the session active? Is it the same as xmpp.client.idle for spark?

It might help to document all the httpbind properties on the openfire properties page.

Thanks

dror wrote:

Does the idle property allow client not to send httpbind request for 3600 ms and keep the session active? Is it the same as xmpp.client.idle for spark?

Yes, that’s exactly it. “Maximum amount of time client can be idle before being considered a time-out.”

It might help to document all the httpbind properties on the openfire properties page.

Yes, I agree. It’s long overdue.

What is the default value of xmpp.httpbind.client.idle?

And what are the default value of the others properties?

xmpp.httpbind.client.requests.max

xmpp.httpbind.client.requests.polling

5sec?

xmpp.httpbind.client.requests.wait

Thanks