Hi Fabian, > You say that you've added support for the client-connect plugin call. May I > ask what was missing?
Nothing dramatic, I just added deferred support for client-connect v2. > So this is basically about replacing a 5s poll-interval with something that > should proceed near instantaneously, correct? Well, 5 seconds interval is still there, it is client-side thing. I made server send push_reply immediately after result is ready (written to ccr file) without waiting for incoming push_request. I noticed that if authentication / authorization happens fast enough, server may send push_reply before push_request is arrived. Sometimes client anyway sends push_request and server sends second push_reply. To avoid that and to follow the protocol (I haven't noticed any issues, though), in latest version I made server wait for the first push_request. So, if authorization takes less than second, client will get response in a second (with first push_request), otherwise immediately when auth is done. I can probably modify client part and make it not send push_request if push_reply has already arrived. Would it be the correct way? > Thanks for sharing! I'll have a look at it, when time permits. Though my > focus is currently on getting some or all of the patches from the basic > patch-set upstream. Indeed it would be great to have your patch in upstream master. -Lev