Received: by 10.66.80.166 with SMTP id s6mr3976453pax.30.1349676387416;
        Sun, 07 Oct 2012 23:06:27 -0700 (PDT)
X-BeenThere: nodejs@googlegroups.com
Received: by 10.68.197.163 with SMTP id iv3ls21379127pbc.9.gmail; Sun, 07 Oct
 2012 23:06:12 -0700 (PDT)
Received: by 10.68.189.37 with SMTP id gf5mr306716pbc.16.1349676372503;
        Sun, 07 Oct 2012 23:06:12 -0700 (PDT)
Date: Sun, 7 Oct 2012 23:06:12 -0700 (PDT)
From: Thuan le minh <leminhthua...@gmail.com>
To: nodejs@googlegroups.com
Message-Id: <be2e3003-0082-4dfb-bcf1-4ee860035d49@googlegroups.com>
Subject: node.js caching proxy
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1834_13771990.1349676372221"

------=_Part_1834_13771990.1349676372221
Content-Type: multipart/alternative; 
	boundary="----=_Part_1835_7380120.1349676372221"

------=_Part_1835_7380120.1349676372221
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

is there solution for node.js caching proxy with bellow scenario 

    1-- (if webserver response data) 
    client <--> node.js proxy <---> webserver 
          (cached data) 
     2-- if webserver not response data
     client ---> node.js proxy    webserver
       <---- cache data
       
thank !

------=_Part_1835_7380120.1349676372221
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

is there solution for node.js caching proxy with bellow scenario <br><br>&nbsp;&nbsp;&nbsp; 1-- (if webserver response data) <br>&nbsp;&nbsp;&nbsp; client &lt;--&gt; node.js proxy &lt;---&gt; webserver <br>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp; (cached data) <br>&nbsp;&nbsp;&nbsp;&nbsp; 2-- if webserver not response data<br>&nbsp;&nbsp;&nbsp;&nbsp; client ---&gt; node.js proxy&nbsp;&nbsp;&nbsp; webserver<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;---- cache data<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; <br>thank !<br>
------=_Part_1835_7380120.1349676372221--

------=_Part_1834_13771990.1349676372221--