Not logged in. · Lost password · Register
Forum: agsXMPP RSS
Avatar
marcelo #1
Member since Jul 2005 · 12 posts
Group memberships: Members
Show profile · Link to this post
Subject: failure to catch server unavailabilty
It's me again. The guy who needs to send messages from inside apps.
I devised a functional test, interacting with a GUI.
If the XMPP server name is correctly entered and alive, it works very well.
But if I enter the wrong server name, the library "hangs" forever.
Of course, a "wrong server name" is like "no server availability". Also, the same effect could be achieved stopping the service ( I'm using Jive Messenger ).
Trying to learn, I tested the "MiniClient" and things go alike: no event is available to catch a Connect failure. MiniClient hangs forever.
I tried to hack a little around ClientSocket.EndConnect ( in the catch section ) but at no luck.

Incidentally, a Dns failure ( could not resolve server name ) goes uncatched also.

But the cure for connection failure could be useful for Dns failure.

TIA

Marcelo

May be it's required a new event: OnConnectionFailure or so.
But I'm not in the place to make such a change on my own.
But if you could guide me a little, I can do and test the change and, of course, contribute the patched code.
Avatar
Alex #2
Member since Feb 2003 · 4317 posts · Location: Germany
Group memberships: Administrators, Members
Show profile · Link to this post
hi marcelo,

yes you are right. This is a problem which is forever now on my TODO and i never finished it ;-)
So its time to add it now. But im currently workint on the next release which will be .NET2 with VS2005. I switched from the Mono.Security library to build in SSL from .NET2. So this code will not work anymore on 2003. Is this a problem for you?

Alex
Avatar
marcelo #3
Member since Jul 2005 · 12 posts
Group memberships: Members
Show profile · Link to this post
Subject: failure ...
Thank you, Alex.

Sadly, I'm tied ( for a year or so, I think ) to NET 1.1 and VS2003.

But I think ( tell me if I'm wrong ) that the socket programming model is not essentially different between net 1.1 and 2.0

So, if you are not making extensive changes to the library event model, I think I could patch the current version, following the new one.

Does it seems possible ?

TIA

Marcelo
Avatar
Alex #4
Member since Feb 2003 · 4317 posts · Location: Germany
Group memberships: Administrators, Members
Show profile · Link to this post
hi marcelo,

no there is not much difference betwwen 1.1 and 2.0. But .NET 2.0 has build in SSL support. And i want to use the new SSL classes. But it should be no big deal to use conditions for NEW and OLD SSL or write a small wrapper.

Alex
Avatar
marcelo #5
Member since Jul 2005 · 12 posts
Group memberships: Members
Show profile · Link to this post
Thank you again, Alex

Have you an estimated release date ?

Marcelo
Avatar
Alex #6
Member since Feb 2003 · 4317 posts · Location: Germany
Group memberships: Administrators, Members
Show profile · Link to this post
hi marcelo,

i implemented a socket error handler. Ping me by mail at gnauck@ag-software.de and i will send you the latest code.
Its .NET 2.0 currently. But will try to add compatibility for .NET 1.1

Alex
Close Smaller – Larger + Reply to this post:
Verification code: VeriCode Please enter the word from the image into the text field below. (Type the letters only, lower case is okay.)
Smileys: :-) ;-) :-D :-p :blush: :cool: :rolleyes: :huh: :-/ <_< :-( :'( :#: :scared: 8-( :nuts: :-O
Special characters:
Forum: agsXMPP RSS