Michael Pasternak has posted comments on this change. Change subject: packaging: disconnecting api instance at the end of all in one ......................................................................
Patch Set 1: i do not limit anything, there are two scenarios 1) 1. a = API() 2. a = API() 2) 1. a = API() 2. b = API() we're talking about scenario #1, in order for #1.2 to work first you should call a.disconnect() to release the resources, the reason for that is to avoid having zombie sessions in the restapi, this is about #1, about #2, unfortunately i have no control over this scenario and rely on programming skills of developer to call .disconnect() when his program exists, otherwise if he created endless session upon sdk construction, it will stay in restapi forever consuming resources and being potential security breach. hope it's clear now. -- To view, visit http://gerrit.ovirt.org/17847 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I8ece6bb8f825606442322a087fd52a647af64ffe Gerrit-PatchSet: 1 Gerrit-Project: ovirt-engine Gerrit-Branch: master Gerrit-Owner: Ohad Basan <oba...@redhat.com> Gerrit-Reviewer: Alon Bar-Lev <alo...@redhat.com> Gerrit-Reviewer: Eyal Edri <ee...@redhat.com> Gerrit-Reviewer: Michael Pasternak <mpast...@redhat.com> Gerrit-Reviewer: Moran Goldboim <mgold...@redhat.com> Gerrit-Reviewer: Ofer Schreiber <oschr...@redhat.com> Gerrit-Reviewer: Ohad Basan <oba...@redhat.com> Gerrit-Reviewer: Sandro Bonazzola <sbona...@redhat.com> Gerrit-HasComments: No _______________________________________________ Engine-patches mailing list Engine-patches@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-patches
