After the recent thread on the list we have decided that we should let
everyone know that the Witango Technologies office will be closed on
Monday the 26th of April. It is a public holiday in Australia as part
of Anzac Day commemorations that take place on Sunday.
The office WILL reopen on
Thanks,
Maybe we can keep the panic from happening for at least part of the day :-)
After the recent thread on the list we have decided that we should
let everyone know that the Witango Technologies office will be
closed on Monday the 26th of April. It is a public holiday in
Australia as part
never mind about my post below... The transactions do what they're
supposed to do, isolate the database transactions from eachother, but
they do not do what I proposed below. The second hit finishes before
the first hit.
If your problem is that you don't want more than 1 DB transaction
You *can* get it to behave the way I explained.
By adding more than just Search Actions or SELECTs to the code inside
of the transaction. You have to have something that creates a
dependency. For example, I can't do a read in hitsecond.taf, because
someone else may have done a write in
Does using Push on a results action clear the @results accumulated so far? If so,
is there a way to accumulate the total HTML results generated if the page is built by
pushing several results actions?
Dave Machin
E-Mail. [EMAIL PROTECTED]
Tel. 805.614.0123 x 30
Address: 3130 Skyway Drive
Push sends the results thus far to the user, but does not send results
already sent (by a previous push). It does not 'clear' anything.
If you want to do something with the accumulated results, you can use
the @RESULTS tag.
Robert
-Original Message-
From: Dave Machin [mailto:[EMAIL
That's what I expected, but in my .taf, it seems that the @RESULTS tag only contains
the results accumulated since (but not including) the most recently pushed action. If
I display the @RESULTS tag in an action immediately after a pushed action @RESULTS is
always empty.
- Original Message
That's correct since the push empties the accumulated results to the
client. That is what should happen.
I've found no reason to use push, and in fact discourage it's usage.
-Original Message-
From: Dave Machin [mailto:[EMAIL PROTECTED]
Sent: Friday, April 23, 2004 7:14 PM
To: [EMAIL
1. push doens't work in Redhat 9/apache2/witango 5-065. it's been
reported as a bug.
2. the push won't work with table rows, because the browser can't build
the table until the table is closed, or the html is closed.
3. I think push can be a useful feedback mechanism during extended
Does anyone have a firm opinion (or even a fairly well gelled one) as
to the relative merits/demerits of using Apache vs. WebSTAR with
Witango on Mac OS X?
I'm talking about the latest versions of each. I searched the archive
but didn't find any clear (at least to me) discussion of this.
Cost
10 matches
Mail list logo
