Porting from Apache 1.3 to Apache 2.0

Porting from Apache 1.3 to Apache 2.0

am 09.10.2002 22:11:59 von souvik

Hi,
I am starting to port my Apache1.3 code to Apache2.0. I have some
questions about some APIs that were present in 1.3 but is not present in
2.0.

* In 1.3, there were APIs like ap_soft_timeout(),
ap_reset_timeout(), ap_kill_timeout() etc. I couldn't find them in 2.0.
I have looked in the web site, downloaded the source code (for both
1.3.27 and 2.0.43). Are there corresponding APIs for 2.0? If not, what
would I replace those calls by in 2.0? Has the programming model
regarding timeouts changed from 1.3 in 2.0?

* In 1.3, I used the method ap_send_http_header(request_rec*). This
no longer seems to be available in 2.0. Has this been replaced by some
other call?

* In 1.3, I used ap_bclose(BUFF*) to close connections etc. How do I
do that in 2.0? The ap_bclose(BUFF*) does not seem to be there in 2.0.

Any help would be sincerely appreciated. Thanks in advance.

-Souvik

ps: I have googled for these issues and didn't have much luck. I am
also looking into the source code (for 2.0 and 1.3) for hints - but
haven't had much success yet.


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Porting from Apache 1.3 to Apache 2.0

am 10.10.2002 17:02:59 von rbb

On Wed, 9 Oct 2002, Souvik Das wrote:

> Hi,
> I am starting to port my Apache1.3 code to Apache2.0. I have some
> questions about some APIs that were present in 1.3 but is not present in
> 2.0.
>
> * In 1.3, there were APIs like ap_soft_timeout(),
> ap_reset_timeout(), ap_kill_timeout() etc. I couldn't find them in 2.0.
> I have looked in the web site, downloaded the source code (for both
> 1.3.27 and 2.0.43). Are there corresponding APIs for 2.0? If not, what
> would I replace those calls by in 2.0? Has the programming model
> regarding timeouts changed from 1.3 in 2.0?

Timeouts in Apache 2.0 are radically different from those in 1.3. For the
most part, you can ignore timeouts, the underlying code will handle them
properly. For more details, look at how timeouts are set on sockets in
2.0.

> * In 1.3, I used the method ap_send_http_header(request_rec*). This
> no longer seems to be available in 2.0. Has this been replaced by some
> other call?

You can safely remove this call from your module. There is a filter that
is responsible for sending headers to the client.

> * In 1.3, I used ap_bclose(BUFF*) to close connections etc. How do I
> do that in 2.0? The ap_bclose(BUFF*) does not seem to be there in 2.0.

You don't need to call anything to close the connection. When the request
is done, the server will handle closing the connection for you. In
reality, you most likely shouldn't have been calling ap_bclose in 1.3
either.

Ryan

>
> Any help would be sincerely appreciated. Thanks in advance.
>
> -Souvik
>
> ps: I have googled for these issues and didn't have much luck. I am
> also looking into the source code (for 2.0 and 1.3) for hints - but
> haven't had much success yet.
>
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>

--

____________________________________________________________ ___________________
Ryan Bloom rbb@apache.org
550 Jean St
Oakland CA 94610
------------------------------------------------------------ -------------------


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Porting from Apache 1.3 to Apache 2.0

am 11.10.2002 00:00:50 von souvik

--------------030500060809030607000907
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Thanks a lot for the help.

* In 1.3, I have used the flag "ap_configtestonly" in my module. This
doesn't seem to be exposed in 2.0. There is a "configtestonly" integer
variable inside the main() function but that is not exposed outside. Is
there any other flag that is exposed in 2.0 to indicate that the server
is started with "-t" or "-T" mode?

Thanks

-souvik

rbb@apache.org wrote:

>On Wed, 9 Oct 2002, Souvik Das wrote:
>
>
>
>>Hi,
>> I am starting to port my Apache1.3 code to Apache2.0. I have some
>>questions about some APIs that were present in 1.3 but is not present in
>>2.0.
>>
>> * In 1.3, there were APIs like ap_soft_timeout(),
>>ap_reset_timeout(), ap_kill_timeout() etc. I couldn't find them in 2.0.
>>I have looked in the web site, downloaded the source code (for both
>>1.3.27 and 2.0.43). Are there corresponding APIs for 2.0? If not, what
>>would I replace those calls by in 2.0? Has the programming model
>>regarding timeouts changed from 1.3 in 2.0?
>>
>>
>
>Timeouts in Apache 2.0 are radically different from those in 1.3. For the
>most part, you can ignore timeouts, the underlying code will handle them
>properly. For more details, look at how timeouts are set on sockets in
>2.0.
>
>
>
>> * In 1.3, I used the method ap_send_http_header(request_rec*). This
>>no longer seems to be available in 2.0. Has this been replaced by some
>>other call?
>>
>>
>
>You can safely remove this call from your module. There is a filter that
>is responsible for sending headers to the client.
>
>
>
>> * In 1.3, I used ap_bclose(BUFF*) to close connections etc. How do I
>>do that in 2.0? The ap_bclose(BUFF*) does not seem to be there in 2.0.
>>
>>
>
>You don't need to call anything to close the connection. When the request
>is done, the server will handle closing the connection for you. In
>reality, you most likely shouldn't have been calling ap_bclose in 1.3
>either.
>
>Ryan
>
>


--------------030500060809030607000907
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit








Thanks a lot for the help.



* In 1.3, I have used the flag "ap_configtestonly" in my module. This doesn't
seem to be exposed in 2.0. There is a "configtestonly" integer variable inside
the main() function but that is not exposed outside. Is there any other flag
that is exposed in 2.0 to indicate that the server is started with "-t" or
"-T" mode?



Thanks



-souvik



wrote:

cite="midPine.LNX.4.21.0210101100260.31776-100000@shell.ntrn et.net">
On Wed, 9 Oct 2002, Souvik Das wrote:



Hi,
I am starting to port my Apache1.3 code to Apache2.0. I have some
questions about some APIs that were present in 1.3 but is not present in
2.0.

* In 1.3, there were APIs like ap_soft_timeout(),
ap_reset_timeout(), ap_kill_timeout() etc. I couldn't find them in 2.0.
I have looked in the web site, downloaded the source code (for both
1.3.27 and 2.0.43). Are there corresponding APIs for 2.0? If not, what
would I replace those calls by in 2.0? Has the programming model
regarding timeouts changed from 1.3 in 2.0?



Timeouts in Apache 2.0 are radically different from those in 1.3. For the
most part, you can ignore timeouts, the underlying code will handle them
properly. For more details, look at how timeouts are set on sockets in
2.0.



    * In 1.3, I used the method ap_send_http_header(request_rec*). This 
no longer seems to be available in 2.0. Has this been replaced by some
other call?



You can safely remove this call from your module. There is a filter that
is responsible for sending headers to the client.



    * In 1.3, I used ap_bclose(BUFF*) to close connections etc. How do I 
do that in 2.0? The ap_bclose(BUFF*) does not seem to be there in 2.0.



You don't need to call anything to close the connection. When the request
is done, the server will handle closing the connection for you. In
reality, you most likely shouldn't have been calling ap_bclose in 1.3
either.

Ryan







--------------030500060809030607000907--