reuse ATE session id about featureprofiles

[greg-dennis]

The IxNetwork logic was really only written to work with the IxNetwork Web Platform. Your Reserve() logic should probably determine which Ixia session you want, whether that be a newly-created session or fetching an existing one from some set of preallocated sessions you've created. If a new one is created, the Release() logic can then delete it. In our experience, creating a new session in reserve is preferable, because IxNetwork tends to misbehave over time with repeated use of the same session. Does that make sense?

[mingyangcisco]

Hi @greg-dennis

Thanks for explaining and sharing the experience. We understood the logic was meant for the Web Platform. We also tried with windows RESTAPI and it worked fine for most of the functions. It makes sense to use the Reserve() function to decide which ATE session to use. We raised PR https://github.com/openconfig/featureprofiles/pull/122/files to have that flexibility. Could you please help check if it's ok? it also makes sense to delete the session in the Release function for ATE. we can hep implement that in the current static binding. should we make the delete session as optional?

[mingyangcisco]

#122