Re: WEBDNA chat
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 45136
interpreted = N
texte = Pedro Rivera wrote:> Has any body created something like that with WEBDNA?There's one running at:http://www.pluto.no/plutoprat/index.tmplActually, WebDNA - or rather WebCatalog - with its ability to create and update files fast, ought to be very well suited for the server side of a chat system.It won't do anything for the client side, though.Basically, the problem is that while a standard web browser can contact a server and *ask* for updates, the server isn't able to contact the browser and say hey, I've got some news for you!The usual way of solving that problem, is to have the client computer run some Java applet or stand-alone application that allows for true two-way communication.An alternative, cruder, method is to use JavaScript or even plain html to get the browser to request updates regularly. The main problem with that solution is that any realistic update frequency would mean a big (with JavaScript) or *ENORMOUS* (with plain html) waste of processing power and bandwith. It might still be good enough for your purposes, though - depends on how much traffic you'd expect.Apparently the pluto.no chatroom uses plain html - no wonder it doesn't seem to be very popular.Frank Nordberghttp://www.musicaviva.com-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list
.To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Pedro Rivera wrote:> Has any body created something like that with WEBDNA?There's one running at:http://www.pluto.no/plutoprat/index.tmplActually, WebDNA - or rather WebCatalog - with its ability to create and update files fast, ought to be very well suited for the server side of a chat system.It won't do anything for the client side, though.Basically, the problem is that while a standard web browser can contact a server and *ask* for updates, the server isn't able to contact the browser and say hey, I've got some news for you!The usual way of solving that problem, is to have the client computer run some Java applet or stand-alone application that allows for true two-way communication.An alternative, cruder, method is to use JavaScript or even plain html to get the browser to request updates regularly. The main problem with that solution is that any realistic update frequency would mean a big (with JavaScript) or *ENORMOUS* (with plain html) waste of processing power and bandwith. It might still be good enough for your purposes, though - depends on how much traffic you'd expect.Apparently the pluto.no chatroom uses plain html - no wonder it doesn't seem to be very popular.Frank Nordberghttp://www.musicaviva.com-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Frank Nordberg
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:
# fields limited? (1997)
(OFF TOPIC) System 8.5.1 FINDER ERROR (1999)
Append command (2000)
WebMerchant 3.0? (1998)
[ShowIf] if the varieable exists (1998)
[WebDNA] Bug in [thisurlplusget] on v7 (2011)
Nesting format tags (1997)
restart needed???? (1997)
Word-And searches (2000)
ErrorLog with Linux? (2000)
Multiple Passwords (1997)
Error -108 (1997)
$append (1998)
PC Authorize & Webmerchant (1998)
Don't know if this is a sily question... (2003)
OSX (2002)
Security Issues and WebCommerce Solution (1997)
sort problems....bug or brain fart? (1997)
question... no field names? (2002)
WebCat2b13MacPlugin - nested [xxx] contexts (1997)