comp.lang.ada
 help / color / mirror / Atom feed
From: "Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>
Subject: Re: Annoucing memcache-ada 0.1
Date: Sun, 16 Jan 2011 23:41:44 +0100
Date: 2011-01-16T23:41:44+01:00	[thread overview]
Message-ID: <op.vpfanufdule2fv@garhos> (raw)
In-Reply-To: 2b5cd851-c148-41f4-95e7-14f235846e6a@q18g2000vbk.googlegroups.com

Le Sun, 16 Jan 2011 23:09:32 +0100, Maciej Sobczak  
<see.my.homepage@gmail.com> a écrit:

> On Jan 16, 9:52 pm, "R. Tyler Croy" <ty...@linux.com> wrote:
>
>> I hope somebody finds it useful, can't wait to see some examples of  
>> caching
>> with AWS! :D
>
> The biggest advantage of AWS, when compared to "traditional" web-
> server hosting stateless scripts, is that AWS is stateful and being an
> in-process part of the complete application makes out-of-process
> caching useless.
> In other words, with AWS there is no need to cache anything in a
> separate process, because data can be stored for future use as a
> regular object in the program. This is not just faster, but also
> safer.
>
> I have to admit, however, that web technologies are not my strongest
> point and I might miss some interesting use cases.
You indeed at least missed an important point : there is *never* something  
like stateful with web process. This is a fundamental consequence of the  
client browsing process. “Stateful web server” concept makes no sense. As  
the user can go back and forward in his/her navigation history, the only  
possible state must be stored in pages stored in the browser, and if ever  
needed, these states informations must be transmitted to the web server  
via POST (preferably, personal feeling). In the web, there is a per-page  
state at the client side, not a per-cession state at the server side.

Of course, many do this error to see state at the server side (and you end  
up with errors and unexpected behaviors from the client point of view).

To talk about caching now, it may take place in so much multiple place  
that there may not be single simple answer. Anyway, caching is in way  
related to a kind of server state. Then, caching applied to static content  
is not the same as caching applied to dynamically generated content. The  
first may be handled by the underlying OS as much as by the server, and  
the second may be as much handled by the client application as much as by  
the server too.

This is not as simply a part of the server solely. This is likely to be  
indeed the topic of a separate process in many cases.

-- 
Si les chats miaulent et font autant de vocalises bizarres, c’est pas pour  
les chiens.

“I am fluent in ASCII” [Warren 2010]



  reply	other threads:[~2011-01-16 22:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16 20:52 Annoucing memcache-ada 0.1 R. Tyler Croy
2011-01-16 22:09 ` Maciej Sobczak
2011-01-16 22:41   ` Yannick Duchêne (Hibou57) [this message]
2011-01-16 22:44     ` Yannick Duchêne (Hibou57)
2011-01-17 10:40     ` Simon Wright
2011-01-17 11:07       ` Yannick Duchêne (Hibou57)
2011-01-17 19:57         ` Simon Wright
2011-01-17 12:13       ` Georg Bauhaus
2011-01-17 19:59         ` Simon Wright
2011-01-17 10:50     ` pascal.obry
2011-01-17 10:57       ` Yannick Duchêne (Hibou57)
2011-01-17 11:02         ` pascal.obry
2011-01-17 11:14           ` Yannick Duchêne (Hibou57)
2011-01-17 12:49             ` pascal.obry
2011-01-16 23:09   ` R. Tyler Croy
2011-01-16 23:47   ` Georg Bauhaus
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox