Re: help with accessing SELECT lists with HTML::Form (Thanks)

On Fri, Aug 22, 2003 at 06:04:11PM -0700, Gisle Aas wrote: Mark Stosberg [EMAIL PROTECTED] writes: I'm having trouble with a particular task with SELECT lists that seems like it should be straight forward. I'm looking for suggestions and sample code to solve this. Here's what I

Re: help with accessing SELECT lists with HTML::Form (with code sample)

On Fri, Aug 22, 2003 at 06:04:11PM -0700, Gisle Aas wrote: Mark Stosberg [EMAIL PROTECTED] writes: I'm having trouble with a particular task with SELECT lists that seems like it should be straight forward. I'm looking for suggestions and sample code to solve this. Here's what I

Re: help with accessing SELECT lists with HTML::Form (with code sample)

On Mon, Aug 25, 2003 at 01:29:11PM -0700, Gisle Aas wrote: Mark Stosberg [EMAIL PROTECTED] writes: Given the name of the selection list, I want to randomly select one of the items in the selection list, and return the value that was selected. It sounds easy, but HTML::Form

a new param function (was: Re: help with accessing SELECT lists...)

On Mon, Aug 25, 2003 at 05:39:54PM -0700, Gisle Aas wrote: Mark Stosberg [EMAIL PROTECTED] writes: Also functions could be added to make it easier to handle inputs with multiple values. For me, I think the functions like CGI.pm's param and append would be must intuitive. These functions

Re: streaming connection with UserAgent

- content-length=3688, ok I would guess that one reason is that content can be sent unbuffered, in a stream. In that case, the ultimate size can't be known ahead of time. Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer [EMAIL

Re: a way to get at form tag attributes?

. Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer [EMAIL PROTECTED] Summersault, LLC 765-939-9301 ext 202 database driven websites . . . . . http://www.summersault.com/ . . . . . . . .

research and reflections on HTTP header ordering (was: Re: [PATCH] FIFO header order support in HTTP::Headers)

that optimization later. --Gisle -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer m...@summersault.com Summersault, LLC 765-939-9301 ext 202 database driven websites . . . . . http://www.summersault.com/ . . . . . . . .

[PATCH] port of performance improvements from HTTP::Headers::Fast

. As I just mentioned in a previous post, it also adds a new method to generate the headers in an unsorted order, for better performance. The behavior of as_string() is not changed. Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal

Re: installation of frameready-1.020 failed

On Wed, 27 Jan 2010 12:47:39 +0100 Yun-an Yan yun-an@uni-rostock.de wrote: Dear All, I cannot pass the test when I try to install Frameready-1.020. Would somebody please help me? Yun-an, The test failed was a live test, meaning it ran against a live website and could have failed for a

Re: Need help for the error 301 moved permanently!

On Thu, 28 Jan 2010 15:51:47 +0530 bipin Nayak nbipi...@gmail.com wrote: Thanks for adding me to this group. Following is the script and result I am getting:- Bipin, I tried the script as you gave it and it gave the source of the login page as the result, *not* a 301. Are you using the

Re: research and reflections on HTTP header ordering (was: Re: [PATCH] FIFO header order support in HTTP::Headers)

to 'as_string'? Could take values like 'sorted'/'original'/'dontcare'. I think that would work equally well, and also allows for backwards compatibility. Mark -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Mark StosbergPrincipal Developer m...@summersault.com

First draft of work published which removes the dependency on HTML::Parser from HTTP::Message

I now have working code published which allows HTTP::Message to work without the dependency on HTML::Parser. This is useful because it's a step towards splitting out some of the HTTP modules into their own distribution which does not have this dependency, which in turn depends on a C compiler.

Re: First draft of work published which removes the dependency on HTML::Parser from HTTP::Message

On Fri, 5 Feb 2010 22:05:27 +0100 Gisle Aas gi...@aas.no wrote: http://dev.w3.org/html5/spec/Overview.html#determining-the-character-encoding specifies how to pre-scan an HTML document to sniff the charset. Would it not be simpler to just implement the algorithm as specified instead of using