public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "ifoox at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/26487] Weird handling of HTTP Headers
Date: Wed, 01 Mar 2006 18:10:00 -0000	[thread overview]
Message-ID: <20060301181006.29056.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26487-12276@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from ifoox at redhat dot com  2006-03-01 18:10 -------
> I gave up and went down the road of a somewhat simpler implementation at 
> the expense of lookup overhead.  In most cases there are fewer than 
> about a dozen headers, so linear searching an ArrayList should not be 
> too bad.

You are right, I think that given this, it should be OK to go for the simpler
implementation for now.

> I think I will get a second opinion from Tromey et al. ...
Good idea. :)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26487


  parent reply	other threads:[~2006-03-01 18:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 21:34 [Bug libgcj/26487] New: " ifoox at redhat dot com
2006-02-27 21:42 ` [Bug libgcj/26487] " ifoox at redhat dot com
2006-02-27 21:44 ` ifoox at redhat dot com
2006-02-27 21:47 ` ifoox at redhat dot com
2006-02-28 11:38 ` mark at gcc dot gnu dot org
2006-02-28 16:26 ` ifoox at redhat dot com
2006-02-28 16:27 ` ifoox at redhat dot com
2006-02-28 16:54 ` daney at gcc dot gnu dot org
2006-02-28 22:05 ` daney at gcc dot gnu dot org
2006-03-01 16:11 ` ifoox at redhat dot com
2006-03-01 17:10 ` ddaney at avtrex dot com
2006-03-01 18:10 ` ifoox at redhat dot com [this message]
2006-03-03 23:24 ` daney at gcc dot gnu dot org
2006-03-03 23:25 ` [Bug classpath/26487] " daney at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060301181006.29056.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).