[Typo3-dev] Typo3 Application Server

[Dmitry Dulepov]

Well, at least all J2EE implementations are slow and require huge amount of
resources. Take BEA, IBM or JBoss. In my opinion using Java for server-side
is a big mistake. I am working with Java server-side solutions for 5 years
now and feel stronger and stronger that Java is a wrong way.

About polling: chat server could send only new lines + changes in the user
list. It saves a lot of traffic...

Dmitry.
----- Original Message ----- 
From: "Michael Scharkow" <mscharkow at gmx.net>
Newsgroups: typo3.dev
To: <typo3-dev at lists.netfielders.de>
Sent: Tuesday, January 25, 2005 10:43 AM
Subject: Re: [Typo3-dev] Typo3 Application Server


...
> Oh, I just meant *any* faster language, like Java (compared to PHP) or
> C, and with big chat engines, I referred to IRCD, like in undernet etc.
>
> BTW: How is the browser notified of updated in the iframe of your chat
> app? I guess it is some kind of polling after a certain interval. So
> conceptually, this scales still bad, because the browser is still
> torturing the server, even if if nothing is updated. It's only that the
> server is more lightweight.
>
> Greetings,
> Michael