From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,c70dc869310ffb51 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,UTF8 Path: g2news2.google.com!news4.google.com!feeder.news-service.com!94.75.214.39.MISMATCH!aioe.org!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: Annoucing memcache-ada 0.1 Date: Sun, 16 Jan 2011 23:41:44 +0100 Organization: Ada @ Home Message-ID: References: <4d335a76$0$43992$742ec2ed@news.sonic.net> <2b5cd851-c148-41f4-95e7-14f235846e6a@q18g2000vbk.googlegroups.com> NNTP-Posting-Host: 8YsgJzdbsnaSVMKLcUWmzQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 User-Agent: Opera Mail/11.00 (Win32) Xref: g2news2.google.com comp.lang.ada:17437 Date: 2011-01-16T23:41:44+01:00 List-Id: Le Sun, 16 Jan 2011 23:09:32 +0100, Maciej Sobczak = a =C3=A9crit: > On Jan 16, 9:52 pm, "R. Tyler Croy" 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* somethi= ng = like stateful with web process. This is a fundamental consequence of the= = client browsing process. =E2=80=9CStateful web server=E2=80=9D concept m= akes 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 eve= r = 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 e= nd = 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 conte= nt = 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 b= y = 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=E2=80=99es= t pas pour = les chiens. =E2=80=9CI am fluent in ASCII=E2=80=9D [Warren 2010]