Hi Bill, I think in this case, two things are happening here when you turn on Push for an Action in a TAF file.
Any output content you have, prior to the Action with Push turned on, is probably being sent to the Browser. This kind of partial output usually triggers an HTTP message that basically says to the Browser "wait, content coming in pieces". This activity tells the browser to wait longer than usual to load content. This is a good thing. The second part is that the Push setting only works once all the code for the given Action is finished. This is the bad part. The content from your Results array will not be sent until the Action is finished, because it's still part of the same Action. I believe the Action has to fully complete before any of it's output can be "pushed" to the browser. You have to either move the rendering outside of the External Action, or maybe play with the PUSH attribute of the <@ROWS> Meta Tag. I've had great success with Push, when I put the "pushed" Action I want to render (and the content I want sent) inside a For Loop Action - then content is sent in pieces on each Loop. In your case, you might have some challenages because the External Action is obviously taking a long time to complete I guess. You might have to rethink how you do this particular process, if want content to be streamed during execution. This kind of functionality is very helpful. In the past I've built quick and dirty code in Witango to handle a special Export or something, and with Push I can make that process run for a hour and the browser doesn't timeout. Hope this helps. Cheers..... Scott Cadillac, XML-Extranet - http://xmlx.ca 403-281-6090 - [EMAIL PROTECTED] Well-formed Development -- Extranet solutions using C# .NET, Witango, MSIE and XML -----Original Message----- From: Bill Conlon <[EMAIL PROTECTED]> To: "Witango-Talk" <[EMAIL PROTECTED]> Date: Wed, 5 Nov 2003 12:05:48 -0800 Subject: Witango-Talk: push for external action > I am running an external action (shell script to invoke the swish-e > indexer). From the command line this returns information line by line > in > the terminal. Likewise, it returns the results to witango in > @@request$resultset. > > I would like to push the results, line by line to the browser. It > seems > like push is operating, because the browser does not time out during > the > two minute indexing run. But results are not displayed in the browser > until indexing is complete. > > Within the Extenal action I have a ResultsHTML attribute. I have tried > both: @@request$results and <@ROWS>@@request$resultset[<@CURROW>,1]<br > /></@ROWS> as the ResultsHTML. Same results with Mac Mozilla 1.5 and > Mac > IE 5.2. > > Any suggestions? > > Bill Conlon > > To the Point > 345 California Avenue Suite 2 > Palo Alto, CA 94306 > > office: 650.327.2175 > fax: 650.329.8335 > mobile: 650.906.9929 > e-mail: mailto:[EMAIL PROTECTED] > web: http://www.tothept.com > > > _______________________________________________________________________ > _ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
