Mailing List Archive: mod_backhand: users

Non Parsed Headers and x-mixed-replace

Index | Next | Previous | View Threaded

Mayes-Iman at Aramark

Feb 13, 2002, 3:03 PM

Post #1 of 6 (825 views)
Permalink

Non Parsed Headers and x-mixed-replace

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1B4DA.426B60BD
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,=20

Don't know if this has been covered yet. If so please forgive me. I have
a CGI that is using non parsed headers (NPH) and x-mixed-replace to
dynamically update the browser. This works fine alone, but with
mod_backhand I cannot seem to get it to work. Is mod_backhand able to
handle this, or is there some configuration thing I'm missing.

Thanks

Iman

------_=_NextPart_001_01C1B4DA.426B60BD
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4712.0">
<TITLE>Non Parsed Headers and x-mixed-replace</TITLE>
</HEAD>
<BODY>


Hi, 


Don't know if this has been covered =
yet. If so please forgive me. I have a CGI that is using non parsed =
headers (NPH)  and x-mixed-replace to dynamically update the =
browser. This works fine alone, but with mod_backhand I cannot seem to =
get it to work. Is mod_backhand able to handle this, or is there some =
configuration thing I'm missing.

Thanks


Iman


</BODY>
</HTML>
------_=_NextPart_001_01C1B4DA.426B60BD--

jesus at omniti

Feb 13, 2002, 10:34 PM

Post #2 of 6 (816 views)
Permalink

Non Parsed Headers and x-mixed-replace [In reply to]

On Wednesday, February 13, 2002, at 05:03 PM, Mayes, Iman wrote:
> Don't know if this has been covered yet. If so please forgive me. I=20
> have a CGI that is using non parsed headers (NPH)=A0 and =
x-mixed-replace=20
> to dynamically update the browser. This works fine alone, but with=20
> mod_backhand I cannot seem to get it to work. Is mod_backhand able to=20=

> handle this, or is there some configuration thing I'm missing.

I am not all that familiar with NPH and x-mixed-replace... So, I have no=20=

clue. If you could give me some insight, I might be able to tell you=20
how mod_backhand is breaking things.

--
Theo Schlossnagle
1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7

Mayes-Iman at Aramark

Feb 14, 2002, 8:52 AM

Post #3 of 6 (824 views)
Permalink

Non Parsed Headers and x-mixed-replace [In reply to]

Basically the way NPH works is that the webserver does not create any
headers (including the 200 OK header) to send back to the browser. The
CGI is responsible for doing so. One of the reasons for doing this is to
use the x-mixed-replace content type. This allows the CGI to send
multiple page updates to the browser in one session (aka Server Push).
For example, lets say I have a CGI that performs some long process
consisting of multiple steps, but I want the user to get continuous
updates during the process. I could push a separate web page at the
completion of each step so that the user can see progress and the
browser won't time out. Another factor which is needed in order for
x-mixed-replace to work properly is that both the webserver and the CGI
must not buffer the updates. If updates are buffered what can happen is
that more than one page will get sent to the browser in one shot, thus
loosing the effect of "progress".

Here is a link that could help out as well:

http://www.netscape.com/assist/net_sites/pushpull.html

Thank you for the quick response.

Iman

-----Original Message-----
From: Theo Schlossnagle [mailto:jesus [at] omniti]
Sent: Thursday, February 14, 2002 12:34 AM
To: backhand-users [at] lists
Subject: Re: [m_b_users] Non Parsed Headers and x-mixed-replace

On Wednesday, February 13, 2002, at 05:03 PM, Mayes, Iman wrote:
> Don't know if this has been covered yet. If so please forgive me. I=20
> have a CGI that is using non parsed headers (NPH)=A0 and =
x-mixed-replace

> to dynamically update the browser. This works fine alone, but with=20
> mod_backhand I cannot seem to get it to work. Is mod_backhand able to=20
> handle this, or is there some configuration thing I'm missing.

I am not all that familiar with NPH and x-mixed-replace... So, I have no

clue. If you could give me some insight, I might be able to tell you=20
how mod_backhand is breaking things.

--
Theo Schlossnagle
1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7

_______________________________________________
backhand-users mailing list
backhand-users [at] lists
http://lists.backhand.org/mailman/listinfo/backhand-users

Mayes-Iman at Aramark

Feb 18, 2002, 10:11 AM

Post #4 of 6 (826 views)
Permalink

Non Parsed Headers and x-mixed-replace [In reply to]

Hi,

Just checking to see if there is anything I can do to help with this
issue.

Iman Mayes

-----Original Message-----
From: Theo Schlossnagle [mailto:jesus [at] omniti]
Sent: Thursday, February 14, 2002 12:34 AM
To: backhand-users [at] lists
Subject: Re: [m_b_users] Non Parsed Headers and x-mixed-replace

On Wednesday, February 13, 2002, at 05:03 PM, Mayes, Iman wrote:
> Don't know if this has been covered yet. If so please forgive me. I=20
> have a CGI that is using non parsed headers (NPH)=A0 and =
x-mixed-replace

> to dynamically update the browser. This works fine alone, but with=20
> mod_backhand I cannot seem to get it to work. Is mod_backhand able to=20
> handle this, or is there some configuration thing I'm missing.

I am not all that familiar with NPH and x-mixed-replace... So, I have no

clue. If you could give me some insight, I might be able to tell you=20
how mod_backhand is breaking things.

--
Theo Schlossnagle
1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7

_______________________________________________
backhand-users mailing list
backhand-users [at] lists
http://lists.backhand.org/mailman/listinfo/backhand-users

george at omniti

Feb 18, 2002, 10:22 AM

Post #5 of 6 (814 views)
Permalink

Non Parsed Headers and x-mixed-replace [In reply to]

I think the question was what Non-Parsed Headers, and x-mixed-replace=20
are. I'm not familiar with those terms. Can you give a technical=20
definition of what they mean?

George

On Monday, February 18, 2002, at 12:11 PM, Mayes, Iman wrote:

> Hi,
>
> Just checking to see if there is anything I can do to help with this
> issue.
>
> Iman Mayes
>
> -----Original Message-----
> From: Theo Schlossnagle [mailto:jesus [at] omniti]
> Sent: Thursday, February 14, 2002 12:34 AM
> To: backhand-users [at] lists
> Subject: Re: [m_b_users] Non Parsed Headers and x-mixed-replace
>
>
>
> On Wednesday, February 13, 2002, at 05:03 PM, Mayes, Iman wrote:
>> Don't know if this has been covered yet. If so please forgive me. I
>> have a CGI that is using non parsed headers (NPH)=A0 and =
x-mixed-replace
>
>> to dynamically update the browser. This works fine alone, but with
>> mod_backhand I cannot seem to get it to work. Is mod_backhand able to
>> handle this, or is there some configuration thing I'm missing.
>
> I am not all that familiar with NPH and x-mixed-replace... So, I have =
no
>
> clue. If you could give me some insight, I might be able to tell you
> how mod_backhand is breaking things.
>
> --
> Theo Schlossnagle
> 1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
> 2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7
>
>
> _______________________________________________
> backhand-users mailing list
> backhand-users [at] lists
> http://lists.backhand.org/mailman/listinfo/backhand-users
>
> _______________________________________________
> backhand-users mailing list
> backhand-users [at] lists
> http://lists.backhand.org/mailman/listinfo/backhand-users
>
>
// George Schlossnagle
// 1024D/1100A5A0=A0 1370 F70A 9365 96C9 2F5E=A056C2 B2B9 262F 1100 A5A0

Mayes-Iman at Aramark

Feb 18, 2002, 10:28 AM

Post #6 of 6 (817 views)
Permalink

Non Parsed Headers and x-mixed-replace [In reply to]

I sent a reply to that earlier, but here it goes again:

[.
Basically the way NPH works is that the webserver does not create any
headers (including the 200 OK header) to send back to the browser. The
CGI is responsible for doing so. One of the reasons for doing this is to
use the x-mixed-replace content type. This allows the CGI to send
multiple page updates to the browser in one session (aka Server Push).
For example, lets say I have a CGI that performs some long process
consisting of multiple steps, but I want the user to get continuous
updates during the process. I could push a separate web page at the
completion of each step so that the user can see progress and the
browser won't time out. Another factor which is needed in order for
x-mixed-replace to work properly is that both the webserver and the CGI
must not buffer the updates. If updates are buffered what can happen is
that more than one page will get sent to the browser in one shot, thus
loosing the effect of "progress".

Here is a link that could help out as well:

http://www.netscape.com/assist/net_sites/pushpull.html

]

I apologize if I am unclear on anything. Let me know if you have
questions.

Thanks.

Iman Mayes

-----Original Message-----
From: George Schlossnagle [mailto:george [at] omniti]
Sent: Monday, February 18, 2002 12:22 PM
To: backhand-users [at] lists
Subject: Re: [m_b_users] Non Parsed Headers and x-mixed-replace

I think the question was what Non-Parsed Headers, and x-mixed-replace=20
are. I'm not familiar with those terms. Can you give a technical=20
definition of what they mean?

George

On Monday, February 18, 2002, at 12:11 PM, Mayes, Iman wrote:

> Hi,
>
> Just checking to see if there is anything I can do to help with this
> issue.
>
> Iman Mayes
>
> -----Original Message-----
> From: Theo Schlossnagle [mailto:jesus [at] omniti]
> Sent: Thursday, February 14, 2002 12:34 AM
> To: backhand-users [at] lists
> Subject: Re: [m_b_users] Non Parsed Headers and x-mixed-replace
>
>
>
> On Wednesday, February 13, 2002, at 05:03 PM, Mayes, Iman wrote:
>> Don't know if this has been covered yet. If so please forgive me. I
>> have a CGI that is using non parsed headers (NPH)=A0 and
x-mixed-replace
>
>> to dynamically update the browser. This works fine alone, but with
>> mod_backhand I cannot seem to get it to work. Is mod_backhand able to
>> handle this, or is there some configuration thing I'm missing.
>
> I am not all that familiar with NPH and x-mixed-replace... So, I have
no
>
> clue. If you could give me some insight, I might be able to tell you
> how mod_backhand is breaking things.
>
> --
> Theo Schlossnagle
> 1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
> 2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7
>
>
> _______________________________________________
> backhand-users mailing list
> backhand-users [at] lists
> http://lists.backhand.org/mailman/listinfo/backhand-users
>
> _______________________________________________
> backhand-users mailing list
> backhand-users [at] lists
> http://lists.backhand.org/mailman/listinfo/backhand-users
>
>
// George Schlossnagle
// 1024D/1100A5A0=A0 1370 F70A 9365 96C9 2F5E=A056C2 B2B9 262F 1100 A5A0

_______________________________________________
backhand-users mailing list
backhand-users [at] lists
http://lists.backhand.org/mailman/listinfo/backhand-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads