Re: [WebDNA] HTTP Streaming -- impossible?
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105553
interpreted = N
texte = --Apple-Mail-1-739368 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I just ran a test, and entering all asterisks in the timer fields, = including the "Second" field, results in a trigger that executes every = second. Give it a try. If you had a trigger that ran once per second and wrote the auction = status to a text or xml file, you could use XMLHttpRequest (AJAX) to = fetch that file from the client page and update the page content with = the results. This would execute very fast, and not bother WebDNA with = every client request, just with the once-per-second trigger. Brian Fries BrainScan Software On Jul 12, 2010, at 1:32 AM, sal danna wrote: > I think you would need 60 triggers like you said. I had been looking = into how auction sites work a while back and found this dissertation = abstract interesting from a business perspective and how it dealt with = the server load issue. I probably would have bought it if I had the = need to build such a site. >=20 > Workload characterization and business-oriented performance = improvement techniques for online auction sites >=20 > Sal >=20 > On Sun, Jul 11, 2010 at 9:36 PM, Kenneth Grome
= wrote: > > Could you use triggers somehow to get the result you need? >=20 > It's a work-around to what I really want to accomplish, but yes I = think I'm going to need 60 separate triggers to do something close to = what I want in webdna. >=20 > Is there a shorthand way to define a single trigger so it will execute = once every second? It looks like a hassle to create 60 separate = triggers, but if I understand the webdna trigger syntax correctly that's = what I'll have to do -- unless there's a better solution ... ? >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us >=20 --Apple-Mail-1-739368 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii I just ran a test, and entering all asterisks in the timer fields, including the "Second" field, results in a trigger that executes every second. Give it a try.
If you had a trigger that ran once per second and wrote the auction status to a text or xml file, you could use XMLHttpRequest (AJAX) to fetch that file from the client page and update the page content with the results. This would execute very fast, and not bother WebDNA with every client request, just with the once-per-second trigger.
Brian Fries
BrainScan Software
On Jul 12, 2010, at 1:32 AM, sal danna wrote:
I think you would need 60 triggers like you said. I had been looking into how auction sites work a while back and found this dissertation abstract interesting from a business perspective and how it dealt with the server load issue. I probably would have bought it if I had the need to build such a site.
Workload characterization and business-oriented performance improvement techniques for online auction sites
Sal
On Sun, Jul 11, 2010 at 9:36 PM, Kenneth Grome
<kengrome@gmail.com> wrote:
> Could you use triggers somehow to get the result you need?
It's a work-around to what I really want to accomplish, but yes I think I'm going to need 60 separate triggers to do something close to what I want in webdna.
Is there a shorthand way to define a single trigger so it will execute once every second? It looks like a hassle to create 60 separate triggers, but if I understand the webdna trigger syntax correctly that's what I'll have to do -- unless there's a better solution ... ?
Sincerely,
Kenneth Grome
--Apple-Mail-1-739368 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I just ran a test, and entering all asterisks in the timer fields, = including the "Second" field, results in a trigger that executes every = second. Give it a try. If you had a trigger that ran once per second and wrote the auction = status to a text or xml file, you could use XMLHttpRequest (AJAX) to = fetch that file from the client page and update the page content with = the results. This would execute very fast, and not bother WebDNA with = every client request, just with the once-per-second trigger. Brian Fries BrainScan Software On Jul 12, 2010, at 1:32 AM, sal danna wrote: > I think you would need 60 triggers like you said. I had been looking = into how auction sites work a while back and found this dissertation = abstract interesting from a business perspective and how it dealt with = the server load issue. I probably would have bought it if I had the = need to build such a site. >=20 > Workload characterization and business-oriented performance = improvement techniques for online auction sites >=20 > Sal >=20 > On Sun, Jul 11, 2010 at 9:36 PM, Kenneth Grome = wrote: > > Could you use triggers somehow to get the result you need? >=20 > It's a work-around to what I really want to accomplish, but yes I = think I'm going to need 60 separate triggers to do something close to = what I want in webdna. >=20 > Is there a shorthand way to define a single trigger so it will execute = once every second? It looks like a hassle to create 60 separate = triggers, but if I understand the webdna trigger syntax correctly that's = what I'll have to do -- unless there's a better solution ... ? >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us >=20 --Apple-Mail-1-739368 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii I just ran a test, and entering all asterisks in the timer fields, including the "Second" field, results in a trigger that executes every second. Give it a try.
If you had a trigger that ran once per second and wrote the auction status to a text or xml file, you could use XMLHttpRequest (AJAX) to fetch that file from the client page and update the page content with the results. This would execute very fast, and not bother WebDNA with every client request, just with the once-per-second trigger.
Brian Fries
BrainScan Software
On Jul 12, 2010, at 1:32 AM, sal danna wrote:
I think you would need 60 triggers like you said. I had been looking into how auction sites work a while back and found this dissertation abstract interesting from a business perspective and how it dealt with the server load issue. I probably would have bought it if I had the need to build such a site.
Workload characterization and business-oriented performance improvement techniques for online auction sites
Sal
On Sun, Jul 11, 2010 at 9:36 PM, Kenneth Grome
<kengrome@gmail.com> wrote:
> Could you use
triggers somehow to get the result you need?
Is there a shorthand way to define a single trigger so it will execute once every second? It looks like a hassle to create 60 separate triggers, but if I understand the webdna trigger syntax correctly that's what I'll have to do -- unless there's a better solution ... ?
Sincerely,
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
multi-paragraph fields (1997)
Looking up two prices in Formulas.db (1997)
Grep question [parsing variables] problem (2003)
country of origin from IPADDRESS??? (2001)
(2000)
MacAuthorize and WebMerchant (1997)
Setting up WebCatalog with Retail Pro data (1996)
Using Plug-In while running 1.6.1 (1997)
Help name our technology! I found it (1997)
OT: Typhoon (1998)
[WebDNA] Double sendmails (2014)
MacAuthorize hub, no modal password dialog? (1997)
HomePage Caution (1997)
[searchString] (1997)
ShowNext Context (2004)
PC Cookie Problem? (2003)
Showif, Hideif reverse logic ? (1997)
Gathering the values of matching fields in a database. (1998)
WebCat2 beta 11 - new prefs ... (1997)
[date] problem with %d%m%Y (1998)