in reply to win32::OLE timeout problem

A trivial search on the monastry (using this google search) produced numerous (nearly 3,000) hits related to timeout e.g. here, here & here ... is that so difficult to do yourself before bothering the monks ??

A user level that continues to overstate my experience :-))

Replies are listed 'Best First'.
Re^2: win32::OLE timeout problem
by BrowserUk (Patriarch) on Apr 01, 2009 at 09:48 UTC
[reply]
      ...in what way ? The OP appears to have given up on an OLE based solution and was asking for any solution.

      Admittedly, the hints I provided didn't directly answer his question, but there were/are, I believe, several pointers that could be of use...

      A user level that continues to overstate my experience :-))
[reply]
        The OP appears to have given up on an OLE based solution and was asking for any solution.

        You cannot do what the OP is trying to do (connect to a remote OLE server), without using OLE.

        His problem is that he doesn't want to wait the default amount of time (1 hour from what I've read), before discovering that the remote server is unavailable.

        Attempting to use alarm will fail dismally as since 5.8.something, Perl's has "safe-signals" which will not interrupt an a individual Perl op-code, never mind a long-running XS function.

        Even if he enables unsafe signals, if alarm had any affect at all, it would probably be disastrous as it would leave the OLE request hanging.

        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom