When WAAGate cannot establish a connection with the WAA
server, users get a message:

"WAA1GATE cannot establish connection to WAA1SRV 10060"

1)  Is there a way to intercept that message and provide a
more friendly message like "The system is down at the
moment, please try later..."

2)  It would also be nice to control the timeout before the
above message is displayed.

Any suggestions?
Yes -- I do have the source code for the gateway, but I
would prefer another solution.

Regards and TIA,

Robert

Ok, forget it.

In the end, I think I will be better off tweaking the source
code for the gateway.  Having never touched the code before,
I was concerned of messing things up but it looks pretty
simple and I have already modified it and compiled it (well,
the message itself at least -- but I'm not sure where the
timeout kicks in yet...).

Robert

Robert,

> In the end, I think I will be better off tweaking the source
> code for the gateway.  Having never touched the code before,
> I was concerned of messing things up but it looks pretty
> simple and I have already modified it and compiled it (well,
> the message itself at least -- but I'm not sure where the
> timeout kicks in yet...).

While you aer at it, would you like me to tell you the change you have to
make to waa1gate.c in order to allow file uploads?

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

To eat, perchance, to barf.

Hi Phil,

> While you aer at it, would you like me to tell
> you the change you have to make to
> waa1gate.c in order to allow file uploads?

What a tease .  Yes, that would be useful !

Robert

Robert,

>> While you aer at it, would you like me to tell
>> you the change you have to make to
>> waa1gate.c in order to allow file uploads?
> 
> What a tease .  Yes, that would be useful !

It's a bit complicated, so I'll send you the source via email with an
explanation.  Basically it's because waa1gate.exe does not properly
allocate sufficient memroy for the data buffer.

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

Of course I tessssted it.

Hi Phil,

> It's a bit complicated, so I'll send you the
> source via email with an explanation.

As always...  Many thanks...

Robert

Hi Phil,

You are the Rocket SocketMan, right?

I figure the connect() function returns error WSAETIMEDOUT
when a connection cannot be made.  After wading through the
MSDN, I still can't seem to find how to adjust the timeout.
Do you know the trick?

Robert

I guess that would be setsockopt() -- yes?

Robert

Robert,

> I guess that would be setsockopt() -- yes?

Yes, but only if using winsock2 - which waa1gate uses 

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

WindowError 025: Uncertainty error. Uncertainty may be inadequate.

Hi Phil,

> > I guess that would be setsockopt() -- yes?
>
> Yes, but only if using winsock2 - which waa1gate uses 

Ok, I tried to use setsockopt with level SOL_SOCKET and
optname SO_RCVTIMEO.  I tried several values for a timeout
but it doesn't seem to have any effect?

I must be doing something wrong or maybe there are other
factors at play (since it seems to vary all by itself -- at
least according to tests done on localhost vs. my ISP).

Anyway this is not critical so I may just forget about it
instead of giving myself a good headache...

Robert