Re: [WebDNA] maybe silly suggestion? [founditems]
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 111959
interpreted = N
texte = Hi Michael! We are extremely mindful when speed is at stake. This why we rewrote = parts of WebDNA, for instance the part that writes to RAM without = flushing to disk. We also use the newest compilers versions and are very = careful about code optimization. WebDNA.fcgi for instance is built for = speed (with certificate activated). A codon or a cell (tag or context) = has no influence on WebDNA speed unless it is interpreted. Also the = current version of WebDNA is one of the slimiest ever. Parsing all files including html can be extremely heavy, but many = developers use this technic without complaining about speed. About the [session] tag, here is how it will work: [sessionstart life=3D3600] will open a session with life in seconds Then, [session] would vehiculate a unique Session Identifier that will = be passed from one page to the other, and/or stored with a name and/or a = shopping cart in a database. [sessionIPcontrol]=3DF/T checks if the original session IP is the same = as the current IP, so the developer can decide if the session survives = an IP change [sessionLIFEcontrol]=3DF/T checks if the life is still valid [sessionend] kills a session A [session] would work with the search engines and would not have any = speed impact. Any other idea will be carefully considered. - chris > On 17 Jan 2015, at 04:23, Michael Davis
wrote: >=20 > If I'm to add my 2=A2 to this... There has to be careful = consideration weighing performance impact vs new tag value. I have no = disagreement with something simple like [realIP], but if a set of = variables can be easily stored in an include file, I am in disagreement = with adding extra code to, for instance, create persistent variables, if = adding the extra code has any negative impact on overall performance. I = like the lean machine that is WebDNA. I'd prefer to only make additions = where either the functionality cannot be achieved within the current = language, or could be made significantly easier without performance = degradation. >=20 > As far as the other teasers, Chris, I have yet to see a method to = maintain session status across stateless/sessionless http requests = without using either javascript, cookies or a session variable. I've = done experimentation with "browser fingerprint" using any and all = headers, but this has never proved to be bulletproof given the = increasing popularity of VPN services and other various proxies. = Javascript has some nifty ways of storing data across pages (and even = domains) but I would be curious how that could be used by WebDNAEngine, = as it would essentially need to be injected into the content of our = documents and of course not work if javascript is disabled. Instead of = leaving us on the edge of our seats, It might be advantageous to all = involved to bring this to group discussion. >=20 >=20 >=20 > Thanks,=20 > Mike > [squarebrackethead] >=20 >=20 >=20 >> On Jan 16, 2015, at 5:35 AM, Kenneth Grome = wrote: >>=20 >>> WebDNA is a different concept ... so don=92t expect WebDNA to >>> start adopting other languages syntax and architecture. >>=20 >> I think this is the right decision. Thanks Chris. >>=20 >> Regards, >> Kenneth Grome >> WebDNA Solutions >> http://www.webdnasolutions.com >> Web Database Systems and Linux Server Management >>=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 > --------------------------------------------------------- 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
Associated Messages, from the most recent to the oldest:
Hi Michael! We are extremely mindful when speed is at stake. This why we rewrote = parts of WebDNA, for instance the part that writes to RAM without = flushing to disk. We also use the newest compilers versions and are very = careful about code optimization. WebDNA.fcgi for instance is built for = speed (with certificate activated). A codon or a cell (tag or context) = has no influence on WebDNA speed unless it is interpreted. Also the = current version of WebDNA is one of the slimiest ever. Parsing all files including html can be extremely heavy, but many = developers use this technic without complaining about speed. About the [session] tag, here is how it will work: [sessionstart life=3D3600] will open a session with life in seconds Then, [session] would vehiculate a unique Session Identifier that will = be passed from one page to the other, and/or stored with a name and/or a = shopping cart in a database. [sessionIPcontrol]=3DF/T checks if the original session IP is the same = as the current IP, so the developer can decide if the session survives = an IP change [sessionLIFEcontrol]=3DF/T checks if the life is still valid [sessionend] kills a session A [session] would work with the search engines and would not have any = speed impact. Any other idea will be carefully considered. - chris > On 17 Jan 2015, at 04:23, Michael Davis wrote: >=20 > If I'm to add my 2=A2 to this... There has to be careful = consideration weighing performance impact vs new tag value. I have no = disagreement with something simple like [realIP], but if a set of = variables can be easily stored in an include file, I am in disagreement = with adding extra code to, for instance, create persistent variables, if = adding the extra code has any negative impact on overall performance. I = like the lean machine that is WebDNA. I'd prefer to only make additions = where either the functionality cannot be achieved within the current = language, or could be made significantly easier without performance = degradation. >=20 > As far as the other teasers, Chris, I have yet to see a method to = maintain session status across stateless/sessionless http requests = without using either javascript, cookies or a session variable. I've = done experimentation with "browser fingerprint" using any and all = headers, but this has never proved to be bulletproof given the = increasing popularity of VPN services and other various proxies. = Javascript has some nifty ways of storing data across pages (and even = domains) but I would be curious how that could be used by WebDNAEngine, = as it would essentially need to be injected into the content of our = documents and of course not work if javascript is disabled. Instead of = leaving us on the edge of our seats, It might be advantageous to all = involved to bring this to group discussion. >=20 >=20 >=20 > Thanks,=20 > Mike > [squarebrackethead] >=20 >=20 >=20 >> On Jan 16, 2015, at 5:35 AM, Kenneth Grome = wrote: >>=20 >>> WebDNA is a different concept ... so don=92t expect WebDNA to >>> start adopting other languages syntax and architecture. >>=20 >> I think this is the right decision. Thanks Chris. >>=20 >> Regards, >> Kenneth Grome >> WebDNA Solutions >> http://www.webdnasolutions.com >> Web Database Systems and Linux Server Management >>=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 > --------------------------------------------------------- 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
christophe.billiottet@webdna.us
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:
Fun with Dates - revisited (1997)
Pop-up menu (1998)
Items XX to XX shown (1997)
Today's suggestions (1998)
Blasted shownext (request for 4.0) (1998)
quitting (1997)
change the number format (1997)
Newspaper Portal (2005)
[cart] not being interpreted inside [founditems] (1997)
RE: Nesting [ListFiles] (1998)
[isfolder] and [filename] (1997)
.. more on sliding discounts... (1997)
Looking for WebCatalog Linux experience/comments. (2001)
[orderfile Orders/[cart]] (2000)
Merchant account (1998)
international time (1997)
Lookup Notfound (1998)
Client-side Image Maps and WebCat? (1998)
WebCatalog & htdig (2000)
POST Datamissing? (1998)