public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Christophe Roux <ch_roux@club-internet.fr>
To: rhug-rhats@sources.redhat.com
Subject: Re: Post request with gcj and tomcat
Date: Mon, 17 Jun 2002 12:06:00 -0000	[thread overview]
Message-ID: <E17K1pd-0006XM-00@smarthost1.mail.easynet.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

Le Lundi 17 Juin 2002 20:49, vous avez écrit :
> I contacted Anthony Green about a problem with servlet using tomcat and
> gcj. As it seems it can interest the community, I send this mail.
> My goal is simple : I want to send a POST Http request from one servlet to
> an other.
> I developed two small servlets M1 and M2 in order to test why it does not
> work so easily.
> The M1 servlet wait for the second M2 which never answers.
> After a few investigations it appears that the
> piece of the puzzle is gnu.gcj.protocol.http.Connection.
> Reading it, I found something strange : it is as if the class uses a
> ServerSocket for doing it's buziness; it starts with writing the header of
> the
> request, then tries to "getHttpHeader", then looks for InpuStream and then
> OutputStream.
> In fact, it should first write the header, then wait for a getOutputStream
> and then a getInputStream.
> I am not very easy with Sockets so I do not know how it works, but I think
> options should tell if input is before or after output.
> I hope I can help you to discover what happens.
> Bye
> Christophe Roux
Here is a scenario for the problem

[-- Attachment #2: scenario3.tgz --]
[-- Type: application/x-gzip, Size: 1905 bytes --]

             reply	other threads:[~2002-06-17 19:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17 12:06 Christophe Roux [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-17 11:47 Christophe Roux

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=E17K1pd-0006XM-00@smarthost1.mail.easynet.fr \
    --to=ch_roux@club-internet.fr \
    --cc=rhug-rhats@sources.redhat.com \
    /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).