Hi Mark,
first of all, thank you to you and Rony for your examples and workarounds.
I had just returned from a month away to a mountain of emails and was in a
sort of despatch them quickly without thinking about them enough mode.
Both methods look really good. I tend to code down grooves and I
The more I think about this the less happy I become.
Rony's solution would also mean that all RDBMS interaction would have to go
through the daemon as it sits on the thread where the connections work, and
so that is not the main thread the interpreter uses.
I don't really understand how
Jon:
On 31.05.2010 17:08, Sahananda (Jon) Wolfers wrote:
The more I think about this the less happy I become.
Don't worry, be happy!
;)
Rony's solution would also mean that all RDBMS interaction would have
to go through the daemon as it sits on the thread where the
connections work, and so
On Mon, May 31, 2010 at 11:08 AM, Sahananda (Jon) Wolfers
sahana...@windhorse.biz wrote:
The more I think about this the less happy I become.
Rony's solution would also mean that all RDBMS interaction would have to go
through the daemon as it sits on the thread where the connections work, and
Mark,
What is the mail thread doing while this is happening? Is it possible
to save the condition data that triggered the failure and pass a
message to the main thread that causes it to reraise the failure
condition?
Rick
On Sun, May 30, 2010 at 12:23 PM, Mark Miesfeld miesf...@gmail.com
Jon:
here is the code of two programs that you should save (watch for
line-breaks).
The first program should be named server.rex, the second
useServer.rex. Invoke as
rexx useServer.rex [nrClients [useReplyInClientToo]]
... nrClients: if not given defaults to '1'
On Mon, May 31, 2010 at 8:30 AM, Rick McGuire object.r...@gmail.com wrote:
What is the mail thread doing while this is happening? Is it possible
to save the condition data that triggered the failure and pass a
message to the main thread that causes it to reraise the failure
condition?
Ah,
Jon:
On 31.05.2010 19:02, Rony G. Flatscher wrote:
here is the code of two programs that you should save (watch for
line-breaks).
The first program should be named server.rex, the second
useServer.rex. Invoke as
rexx useServer.rex [nrClients [useReplyInClientToo]]
... nrClients:
Hi Rony,
thanks for these.
I will study them and try to adapt them and get back to you, but it may take
a day or two.
thanks,
Jon
On 31 May 2010 21:15, Rony G. Flatscher rony.flatsc...@wu-wien.ac.atwrote:
Jon:
On 31.05.2010 19:02, Rony G. Flatscher wrote:
here is the code of two
Hi Rony,
Happiness is proving to be a little more ellusive than that.
Rexx\SQL is thread-safe as of Version 2.5 where the Database client software
is thread-safe.
Rexx\SQL reports whether the client is known to be thread safe by the
variable SUPPORTSTHREADS.
SUPPORTSTHREADS is 1 where the
10 matches
Mail list logo
