Thanks for your replies. There is a way to create a request rec using function: ap_read_request(conn_rec *).
now conn_rec could be created using ap_run_create_connection function which takes pool, socket, bucket and some other arguments. I waasnt sure how to get socket information as we cannot use the connection of any current request_rec for that. It would be really helpful if you can suggest me some pointers for this. Thanks, Parin. On 8/8/05, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote: > At 05:15 AM 8/8/2005, Graham Leggett wrote: > >Parin Shah said: > > > >> we can store the original request_req which was used when the page was > >> served from cache, and then use it as a parameter to the above method. > >> Is this approach is fine? > > > >This isn't very clean, a request_req is just a structure, they should be > >relatively simple to make. Look for the code within the core that brings > >the request_req into existence for the first time, you should be able to > >see how it gets created. > > Actually I'd suggest you use the core to create that request_rec, > rather than chasing upgrades for all the things you need to add > custom when the structure changes. The request_rec can and does > grow on mmn minor bumps, so that's an extra reason to avoid ever > allocating one yourself. You will have very minimal ABI compat > if you allocate your own, and should probably emit a warning on > startup if you see the mmn minor has moved. > > Bill > > >
