> Well.. the problem is not the "function returns immediatly".. it's just that
> we need UI events to get processed to avoid the windows freezing...
> You also told me on MSN that the host resolving is fast.. yes it IS fast...
> I already tested this, it takes very few milliseconds to get the ip of
On Thu, Aug 7, 2008 at 5:33 PM, Álvaro J. Iradier <[EMAIL PROTECTED]>wrote:
> On Thu, Aug 7, 2008 at 11:15 PM, Youness Alaoui
> <[EMAIL PROTECTED]> wrote:
> > Yep, nice to see you back! :)
> >
> > Anyways, here are my ideas :
> >
> > 1 - for the wrapping of socket, you could do something like :
>
On Thu, Aug 7, 2008 at 11:15 PM, Youness Alaoui
<[EMAIL PROTECTED]> wrote:
> Yep, nice to see you back! :)
>
> Anyways, here are my ideas :
>
> 1 - for the wrapping of socket, you could do something like :
>
> proc socket { host port } {
>
>set var "::socket_wait_var_$host"
>
>set $var ""
>
Yep, nice to see you back! :)
Anyways, here are my ideas :
1 - for the wrapping of socket, you could do something like :
proc socket { host port } {
set var "::socket_wait_var_$host"
set $var ""
resolve_hostname $ip [list socket_resolver_callback $var]
tkwait $var
set sock [::tk
thanks for your work, and welcome back :)
On Thu, Aug 7, 2008 at 20:18, Álvaro J. Iradier <[EMAIL PROTECTED]> wrote:
> Sorry for the previous blank email...
>
> ok, further investigation shows most time in GotSOAPReply is spent in
> 'xml2list' (XML time) and in the callbacks (CB time):
>
> SOAPReq
Sorry for the previous blank email...
ok, further investigation shows most time in GotSOAPReply is spent in
'xml2list' (XML time) and in the callbacks (CB time):
SOAPRequest time: 250623 microseconds per iteration
XML time: 132933 microseconds per iteration
CB ::SSOAuthentication1 Authentica
On Thu, Aug 7, 2008 at 7:31 PM, Álvaro J. Iradier <[EMAIL PROTECTED]> wrote:
> HI, the other day, talking to youness we thought amsn was being quite
> unresponssive on start and connection due to sockets blocking while
> resolving the host names (that is, the dns resolution was being
> synchronous
HI, the other day, talking to youness we thought amsn was being quite
unresponssive on start and connection due to sockets blocking while
resolving the host names (that is, the dns resolution was being
synchronous and blocking, even when the sockets are asynchronous).
I made a small tcl extension
