Re: Objectifying a request

Rajeev Bansal <[email protected]>
Newsgroups gmane.comp.web.polipo.user
Message-ID <CAM05QofXsGJL5zxbzdg213QDwWad3igXU1kioXsKKM0Sq8i8-A@mail.gmail.com>
Thanks Juliusz, but why do we need to convert a request or response in
a Object, one can keep it in the form of stream buffer and keep
processing it.

Thanks,
-Rajeev

On Sat, Mar 24, 2012 at 11:50 PM, Juliusz Chroboczek <[email protected]> wrote:
>>   I have a query about the Objectifying a request which is arriving
>> from the client, why do we need to convert a request into object using
>> makeObject() and then process it. Polipo does it in this way due to a
>> performance reason or caching become easy or there is some other
>> reason behind it. Please help me to understand.
>
> A Request represents a GET or POST request that's currently in progress,
> either on the client side or the server side.
>
> An Object represents an entity -- the thing that's returned by the web
> server.  At any given time, an object can have up to one server-side
> request, and any number of client-side requests (if multiple clients are
> requesting the same entity).
>
> -- Juliusz

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.