Re: Stop() behaviour & Access Violation (General questions)

by wodSupport, Wednesday, January 04, 2006, 19:26 (6681 days ago) @ wodSupport

What I think could be happening here is that you hold references to Users object, so that when we release it (in Stop method) it's not destroyed.

I can change wodSSHServer so it kills connections when Stop is called, even collection of users isn't destroyed by itself. I guess this is a safe precaution, but I'm not sure if it will still solve your problem.

locked

3460 views

Complete thread:

Stop() behaviour & Access Violation - David Lucas, 2006-01-04, 16:16
- Re: Stop() behaviour & Access Violation - wodSupport, 2006-01-04, 19:24
  - Re: Stop() behaviour & Access Violation - wodSupport, 2006-01-04, 19:26
    - Re: Stop() behaviour & Access Violation - wodSupport, 2006-01-04, 19:42
      - Re: Stop() behaviour & Access Violation - wodSupport, 2006-01-06, 01:41

The wodCrypt product is great and we appreciate your effort to add support for UNIX Crypt.

William Ruf

Siemens Information and Communication Networks

Thank you for the great customer service ... I am really impressed with the wodSSH ActiveX control.

Andrew Ross

Kiwi Enterprises

WeOnlyDo!COM will be the first stop I make should I require any further off-the-shelf components.

Dean Keigan

RBC Capital Markets

You have been great as far as offering support is concerned and has been extremely responsive to both support requests and suggestions for product enhancements.

David Keenan

Serengeti Systems Incorporated

Thank you very much for the rapid responses. I was a little nervous about dealing with a company that is on a different continent from me. You have proven my concerns to be unfounded.

Robert Pacheco

Surebridge, Inc.