[SOLVED] Why isn't Zimbra UI sending NoOpRequests?

[rht]

I am integrating Zimbra UI with our backend server. I have enabled IM messages and I can see the roster but the UI is not sending the NoOpRequest as frequently as it should.

Do I need to send something more in the notify block of IMGetRosterResponse other than the elements given below?


<notify>
[
<im>
[
// Asynchronous Roster Response
<n type="roster">
</n>
]?

[
<n type="subscribed" to="TOADDR" name="NAME" groups="">
]*

[
// Presence update for a specific user
<n type="presence" from="FROMADDR" [show="ONLINE"]/>
]*

</im>]
]?
</notify>

[rht]

[HOPEFULLY SOLVED]
"Enable instant notifications" is not checked.

[fernandoflorez]

I haven't had the chance to check out how im works (yet) but i think they use comet so they don't need the nooprequest call.

The nooprequest calls are only done when the application is idle.

[rht]

Confirmed,
Zimbra Web Client uses nooprequest for IM. After "Enable instant notifications" preference is set to true, the web client will not wait for the application to be idle rather, it sends a nooprequest in rapid fire mode. With this preference enabled, as soon as the server responds to the first nooprequest, web client will send a second one nooprequest and so on.

Now my next problem is to find what triggers the web client to open a chat window when an incoming message is received. I am sending <im> tag with the message content but Web client does not show it.

I am able to send the message from the web client to Pidgin just fine.

[fernandoflorez]

Thats comet i think. When the gui send nooprequest does the response comes back instantly without new modifications?

Comet will make a request and the server will retain the response (and the connection as open) while there is no changes (notifications in our case). As soon as a response comes back it will open another channel.

I'll check how im stuff works this weekend.