When developing applications using lapi in .Net C#

Nair_Krishnankutty_(nairkrishnankutty_-_(deleted))

When developing applications using lapi in .Net C#Which is the preferred method,The application is a desktop database app,which puts documents into livelink with cats/atts metadata for that matter the app should work against any DMS that supports API calls.a)For readabilty and maintaianability,the different componenents of the class are spread amongst several functions.b)Does invoking a session first and passing them amongst the different functions suffice orFor every function the session constructor is invoked againFor eg Main calls myAddCategories,myAddDocuments,myCreateFolders etc etcIn each of these functions the session is created from scratch.Does each session cause a thread connection in the llserver and is it intensive on the llserverWhat tells livelink the session is not needed anymore.Looking at the docs"The LLSession class encapsulates all of the information needed to create and maintain a Livelink database connection" the maintain part is what is worrying me areall these sessions going to slow/increase the DB calls.I guess what I am asking is while both approaches will work is there a preferred way...