Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KeePassConnection Management #142

Open
jkdba opened this issue Jun 20, 2018 · 0 comments
Open

KeePassConnection Management #142

jkdba opened this issue Jun 20, 2018 · 0 comments

Comments

@jkdba
Copy link
Member

jkdba commented Jun 20, 2018

This needs to be looked into for viability.

Current thoughts are:

Passing the Connection Object should be a performance boost.

Create it as a Module Variable?

Add Handling for closing the Connection. This would mean adding functions to manage connections similar to how pssessions, jobs, or cimsessions work.

If the connection is not closed after each operation then the passed objects can be worked on directly this is a performance boost.

This could also mean that moving objects between databases would be much easier.

Returned Objects could contain a session ID as an origin session then this could be used a default operating connection. If this is done then a -KeePassConnection Parameter will need to be added to each object supporting function so it could be overrided and support pipeline and gathering the default session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant