[Q] How can I run Comet?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I've installed latest version of Comet in squeaksource.com but only got
this error message when I access to comet/chat application.

"
Internal Server Error

Error: Streaming-server required.
"

Is there any more steps other than installing latest seaside and
scriptaculous?

Thanks in advance.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE+T5ZQqspS1+XJHgRAtExAJ912ydBr8NREYOpB5fybT6Q8FQ4swCfTsdb
l5jPvMMvDUhRVwlwTrU2koA=
=yCxr
-----END PGP SIGNATURE-----
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> I've installed latest version of Comet in squeaksource.com but only got
> this error message when I access to comet/chat application.

WAKom stop.
WAListener startOn: 8080

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, it just works. Why WAListener should start on 8080? Can I change
this port number to others, namely 9090?

Thanks in advance.

Lukas Renggli wrote:
>> I've installed latest version of Comet in squeaksource.com but only got
>> this error message when I access to comet/chat application.
>
> WAKom stop.
> WAListener startOn: 8080
>
> Lukas
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE+jgAQqspS1+XJHgRAjvAAJ0bbRbuhGlWK4WqZ43J2fzd7kaMNwCcDplZ
OO61Vg2kGRJIRJG/W6i0QLg=
=6Qvx
-----END PGP SIGNATURE-----
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

What is the order of importance for making Squeak run quickly
when considering: ram, hard drive speed, and cpu speed?
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On 2-Sep-06, at 8:45 PM, Grant Rettke wrote:

> What is the order of importance for making Squeak run quickly
> when considering: ram, hard drive speed, and cpu speed?
In my experience, the three things you need most for good Smalltalk  
performance are, in order
memory bandwidth,
memory bandwidth,
and memory bandwidth.
Cpu speed is surprisingly close to irrelevant except inasmuch as it  
can fill your memory bandwidth. Most of what Smalltalk does is follow  
pointer chains and copy bits around. Doing that fast needs memory  
bandwidth from the cache to cpu, from cache to main memory and main  
memory to display. A bigger cache substitutes somewhat for more  
bandwidth, so long as the cache fill/flush algorithm doesn't bite  
you. A faster cpu can in some cases obviate the need for some of the  
moving bits around and so substitute for some more bandwidth.

My belief is that a 1GHz cpu with a 1GHZ really-truly random access  
speed memory would run rings around current x86/ppc/sparc systems.  
It's a fairly safe bet, since the odds of actual 1GHz memory  asre  
currently slim.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Oxymorons: Military Intelligence


_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Hi, it just works. Why WAListener should start on 8080? Can I change
> this port number to others, namely 9090?

Sure you can run it on any port. WAListener is a replacement to WAKom
though, so I don't see a point in running WAKom in parallel.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> memory bandwidth,
> memory bandwidth,
> and memory bandwidth.

What about memory latency, memory latency and memory latency?

Perhaps not Smalltalk related, but certainly interesting if you want to
gain a deeper understanding in this area are the webcasted lectures of
CS252 at Berkeley.

http://vlsi.cs.berkeley.edu/cs252-s06/index.php/Computer_Science_252

Z.

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Oh. Then, what's the difference between WAListener and WAKom(and
WAKomEncoded)? And why WAListener can run Comet application, but WAKom
can not. What I want to know is this.

Thanks in advance.

Lukas Renggli wrote:
>> Hi, it just works. Why WAListener should start on 8080? Can I change
>> this port number to others, namely 9090?
>
> Sure you can run it on any port. WAListener is a replacement to WAKom
> though, so I don't see a point in running WAKom in parallel.
>
> Cheers,
> Lukas
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE+ubHQqspS1+XJHgRAn1OAKCdNQub4VMge2951nrcZWb3zxjZvgCfbban
ATr0zzAncnQkhxQ5y6hyYA0=
=LgNi
-----END PGP SIGNATURE-----
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Oh. Then, what's the difference between WAListener and WAKom(and
> WAKomEncoded)? And why WAListener can run Comet application, but WAKom
> can not. What I want to know is this.

- WAKom is directly using the Kom server. It requires the full
response of Seaside to actually respond to the client.

- WAListener is implementing its own listening loop. It processes the
request using the mechanisms provided by Kom but directly streams back
the result to the socket instead of waiting for Seaside to complete
the whole request. This is much more efficient as it doesn't require
an intermediate stream to write too and it pushes the result to the
browser immediately. Though, as far as I know, it is less tested and
could potentially be buggy.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It seems that WAListener only can manage comet like persistent(?)
connection - so WAListener can run comet applications but WAKom cannot,
am I right?

Thanks again in advance.

Lukas Renggli wrote:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE+3/6QqspS1+XJHgRApxVAJ46E97Yij8qsD5x7iSNtkS/7SqjugCeKcFj
Ofj4S4xNIBV0GigWyTGbMME=
=r9E/
-----END PGP SIGNATURE-----
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> It seems that WAListener only can manage comet like persistent(?)
> connection

No, WAListener was not made for persistent connections, but to enable
Seaside to generated output right from the beginning:
<http://lists.squeakfoundation.org/pipermail/seaside/2006-January/006455.html>.

It was just good luck that its possible to use Comet with WAListener.
Still I have to do some dirty tricks that the connection is not
closed, such as to manually manually clean up the call-stack and
terminate the initial server thread.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside