No, outer components do not need to be aware of inner components possible call candidates, that would make the system unusably complicated.
Cheers!
-Boris (via BlackBerry)
----- Original Message -----
From: seaside-bounces(a)lists.squeakfoundation.org <seaside-bounces(a)lists.squeakfoundation.org>
To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org>
Sent: Sun Feb 24 20:56:46 2008
Subject: Re: [Seaside] Re: Help with understanding how #call: works
Malte Zacharias wrote:
<snipage>
> I hope this clears it up a bit..
>
Not really. What I'm looking for is this, if component A includes
component B, but inside of B, it calls component C, what happens?
I assume C renders *in place* of B and the rest of A works as it did
before? Is this correct?
If so, does A have to include C in its children as well as B?
It is possible I totally don't understand this stuff.
--
Jeffrey Straszheim
http://straszheim.50megs.com
_______________________________________________
seaside mailing list
seaside(a)lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
What are the restrictions for the free version of Gemstone/S for multi-core
CPUs?
[This question triggered by recent spate of activity with Squeak Hydra-VM,
which offers quite attractive small-to-medium scaling].
Thanks - Sophie
Hi,
I tried the Magma SeasideHelper Todo List Tutorial at
http://wiki.squeak.org/squeak/6021. I found two things
missing:
- In order to use the App some has to install Scriptaculous
and Cryptography (maybe should be added to the squeak
page)
- The example does not work for me. The
StMagmaCollectionDatabase class>>modelKey
contains a missing class. Removing the whole selector
made it work for me.
Norbert
Hi all!
I have a problem in configuring seaside and apache.
I have a domain name, lets say www.example.org, which points to a
machine (lets say machine.my.org) in which I have my apache server
running.
With an html web site, stored on the hard disk, what I would do is to
configure apache like this:
<VirtualHost *:80>
ServerName www.example.org
DocumentRoot /var/www/example
</VirtualHost>
and like this, if I go to www.example.org I will see the web site
located in my server under /var/www/example, while on the browser I
will see the url www.example.org and NOT machine.my.org
The question is: how do I do the same with seaside?
If I use the rewrite module of apache, with this configuration:
<VirtualHost *:80>
ServerName www.example.org
RewriteEngine On
RewriteRule ^/(.*)$ http://localhost:8008/seaside/go/example/$1 [P,L]
</VirtualHost>
I will be redirected to the correct seaside web site, but in the
browser I will see the url machine.my.org:8008/seaside/go/example/
Many thanks and cheers
Marco D'Ambros
Hi,
I've been browsing some Seaside examples (Squeak Source, this time)
and I noticed a pattern where a call: is made replacing the current
component with no expectation of return. For example, when navigating
to the home page, the home component is called but it will never
return to whatever component it's replacing. At least, that's what
happening if I'm reading the code correctly. Is that the common way to
handle such situations?
--
Ronaldo Ferraz
http://log.reflectivesurface.com
Howdy,
I almost have a business partner convinced to give Seaside a try for an
upcoming web project. However, although I love the ideas behind the
technology, and I would love to use Smalltalk on a real paying gig, I
have a deep fear that if we get heavy traffic the system wouldn't keep up.
So, does anyone on this list have experience using Seaside in a high
traffic scenario. I'm talking 200+ hits per second at least. How did
it handle the load? What sort of hardware did you choose? What load
balancing? What database?
--
Jeffrey Straszheim
http://straszheim.50megs.com
That kind of navigation is not uncommon. Imagine making a flight reservation, reviewing the checkout page and clicking on header navigation to get back to the home page. I would hate to be limited to next and previous buttons in that situation. If your component never answers, so be it. But you can always hit back in your browser and proceed and that's the whole point IMHO.
Cheers!
-Boris (via BlackBerry)
----- Original Message -----
From: seaside-bounces(a)lists.squeakfoundation.org <seaside-bounces(a)lists.squeakfoundation.org>
To: 'Seaside - general discussion' <seaside(a)lists.squeakfoundation.org>
Sent: Thu Feb 21 19:34:57 2008
Subject: RE: [Seaside] Re: Navigating away from call:'s
> Maybe, but the home example was just one of many possible. What is the
> user is in the midst of an edition and just clicks away?
>
Cliks away is just too wide. You probably want to include in that editor only
anchors who has callbacks with sense for an edition context. For example an
explicit save or cancel. By saying 'clicks away' you are suggesting just a
different kind of post cancel action?
Sebastian
_______________________________________________
seaside mailing list
seaside(a)lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Do you know if common browsers support those properly?
Cheers!
-Boris (via BlackBerry)
----- Original Message -----
From: seaside-bounces(a)lists.squeakfoundation.org <seaside-bounces(a)lists.squeakfoundation.org>
To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org>; Seaside - developer list <seaside-dev(a)lists.squeakfoundation.org>
Sent: Thu Feb 21 22:16:17 2008
Subject: [Seaside] Set-Cookie2 support in Kom and Swazoo
Hi
Looking at improving the cookie support in Seaside I found out that
neither the latest Kom nor the latest Swazoo support Set-Cookie2 (RFC
2965 from 2000). the Discard attribute looks especially well suited
for session cookies. Sure I could hack it in myself, but I feel this
is more the responsibility of the server vendors.
Any takers?
Cheers
Philippe
_______________________________________________
seaside mailing list
seaside(a)lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
ODBC indeed; we're on VisualWorks and support there is quite solid.
Cheers!
-Boris (via BlackBerry)
----- Original Message -----
From: seaside-bounces(a)lists.squeakfoundation.org <seaside-bounces(a)lists.squeakfoundation.org>
To: 'Seaside - general discussion' <seaside(a)lists.squeakfoundation.org>
Sent: Thu Feb 21 23:16:02 2008
Subject: RE: [Seaside] I need success stories
> We have build a horizontally scalable system by putting F5
> routers in front of X number of Seaside instances with a SQL
> Server backend. BIG-IP offloads SSL, caches all static
> resources and load balances using sticky sessions. Computing
> cycles and RAM are cheap, so I suspect getting a respectable
> throughput is just a matter of adding more gateways in the
> back, but don't quite have the numbers yet.
>
> Cheers!
>
> -Boris (via BlackBerry)
What are you accessing Sql Server with, ODBC?
Ramon Leon
http://onsmalltalk.com
_______________________________________________
seaside mailing list
seaside(a)lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
We have build a horizonally scalable system by putting F5 routers in front of X number of Seaside instances with a SQL Server backend. BIG-IP offloads SSL, caches all static resources and load balances using sticky sessions. Computing cycles and RAM are cheap, so I suspect getting a respectable throughput is just a matter of adding more gateways in the back, but don't quite have the numbers yet.
Cheers!
-Boris (via BlackBerry)
----- Original Message -----
From: seaside-bounces(a)lists.squeakfoundation.org <seaside-bounces(a)lists.squeakfoundation.org>
To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org>
Sent: Thu Feb 21 19:04:50 2008
Subject: [Seaside] I need success stories
Howdy,
I almost have a business partner convinced to give Seaside a try for an
upcoming web project. However, although I love the ideas behind the
technology, and I would love to use Smalltalk on a real paying gig, I
have a deep fear that if we get heavy traffic the system wouldn't keep up.
So, does anyone on this list have experience using Seaside in a high
traffic scenario. I'm talking 200+ hits per second at least. How did
it handle the load? What sort of hardware did you choose? What load
balancing? What database?
--
Jeffrey Straszheim
http://straszheim.50megs.com
_______________________________________________
seaside mailing list
seaside(a)lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside