Re: Invalid state. Not connected (General questions)
Ala,
you cannot use Blocking AND events. When you set Blocking = True and execute method from within an event, application freezes - you have noticed that.
But if you use ASP.NET then you MUST use Blocking = True, otherwise your page will be returned to the client before wodSFTP manages to connect in the background! Async behavior doesn't suit you now. Do you agree with me?
I do completely agree with you :).
as for blocking you mean that if I removed the Connected event implementation the application won't freeze without resetting blocking to false?
Complete thread:
- Invalid state. Not connected - Ala' Yasin, 2005-05-19, 09:13
- Re: Invalid state. Not connected - wodSupport, 2005-05-19, 10:04
- Re: Invalid state. Not connected - Ala, 2005-05-19, 10:25
- Re: Invalid state. Not connected - wodSupport, 2005-05-19, 10:37
- Re: Invalid state. Not connected - Ala, 2005-05-19, 10:48
- Re: Invalid state. Not connected - wodSupport, 2005-05-19, 10:51
- Re: Invalid state. Not connected - Ala', 2005-05-19, 10:55
- Re: Invalid state. Not connected - wodSupport, 2005-05-19, 11:25
- Re: Invalid state. Not connected - Ala', 2005-05-19, 10:55
- Re: Invalid state. Not connected - wodSupport, 2005-05-19, 10:51
- Re: Invalid state. Not connected - Ala, 2005-05-19, 10:48
- Re: Invalid state. Not connected - wodSupport, 2005-05-19, 10:37
- Re: Invalid state. Not connected - Ala, 2005-05-19, 10:25
- Re: Invalid state. Not connected - wodSupport, 2005-05-19, 10:04