Tya vs. shuJIT

2001-01-29 Thread Volker

Hello,

does anyone know which JIT is faster - Tya or shuJIT?

Best regards

Volker


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




server sees no body when doing HTTP POST

2001-01-29 Thread Steinar Bang

Platform: SuSE linux 6.2 (w/kernel version 2.2.14), Blackdown JDK 1.1.7v3

I've been trying to write a small test program that writes a
multipart/form-data body to an apache Tomcat servlet, using HTTP
POST. 

What happens is that the servlet sees the headers, but not the body of 
the message I'm trying to write.  

What I'm wondering is if I've encountered a well known problem with
1.1.7v3?  Or if the problem is something in my code?

I've tried searching the net for this problem, but I haven't found
anything useful yet.

Basically I'm trying to do the same thing that happens when sending
the results of a form from a web browser.

To do some more testing I've written a small cgi-script, which just
writes back the body it receives:

#!/usr/bin/perl
print "Content-type: text/plain", "\n\n";
while (<>) {
print;
}
exit (0);

When I try POSTing a form from a browser, I see the
multipart/form-data it writes.  When I try using my Java application I 
just get the result codes.

Attached is the code I'm using.  Upload.java contains the program, and 
RepositoryCmd.java tries to encapsulate the construction and POST of
the multipart/form-data message.


- Steinar



import java.io.*;

class Upload {
public static void main(String[] args)
{
if (args.length < 3) {
System.out.println("usage: Upload server repository file"
   + " [servlet]");
return;
}

String server = args[0];
String repository = args[1];
String filename   = args[2];
RepositoryCmd rc = null;
if (args.length > 3) {
String servlet   = args[3];
rc = new RepositoryCmd(server,
   repository,
   "put",
   filename,
   servlet);
} else {
rc = new RepositoryCmd(server,
   repository,
   "put",
   filename);
}
System.out.print("Starting upload...");
BufferedReader in = rc.send();
try {
String inputLine;
while ((inputLine = in.readLine()) != null) 
System.out.println(inputLine);
} catch (IOException e) {
System.out.println(e);
}
System.out.println("finished!");
}
}


import java.io.*;
import java.net.*;

class RepositoryCmd {
protected String servlet_;
protected String server_;
protected String repository_;
protected String command_;
protected String filename_;

public RepositoryCmd(String server,
 String repository,
 String command,
 String filename)
{
server_ = server;
repository_ = repository;
command_ = command;
filename_ = filename;
servlet_ = "/metis/repository";
}

public RepositoryCmd(String server,
 String repository,
 String command,
 String filename,
 String servlet)
{
server_ = server;
repository_ = repository;
command_ = command;
filename_ = filename;
servlet_ = servlet;
}

public BufferedReader send()
{
BufferedReader retval = null;
try {
String boundary = "12345xyzzy";
URL repository = new URL("http://" + server_ + servlet_);
HttpURLConnection tc =
(HttpURLConnection)repository.openConnection();
tc.setDoOutput(true);
tc.setDoInput(true);
tc.setAllowUserInteraction(false);
tc.setRequestMethod("POST");
tc.setRequestProperty ("Content-Type",
   "multipart/form-data; "
   + "boundary=" + boundary);
PrintWriter out = new PrintWriter(tc.getOutputStream());
//PrintWriter out = new PrintWriter(System.out);
retval = new BufferedReader(new InputStreamReader(tc.getInputStream()));
FileInputStream fin = new FileInputStream(filename_);
String inputLine;
BufferedReader in =
new BufferedReader(new InputStreamReader(fin));
printPartHeader(out,boundary,"filename","filename_");
while ((inputLine = in.readLine()) != null) {
out.println(inputLine);
}
printPartHeader(out,boundary,"request","");
out.println(command_);
printPartHeader(out,boundary,"path","");
out.println(repository_);
printPartHeader(out,boundary,"overwrite","");
out.println("true");
printPartHeader(out,boundary,"create","");
out.println("true");
 

Re: Tya vs. shuJIT

2001-01-29 Thread Andreas Rueckert

Hi!

On Mon, 29 Jan 2001 Volker wrote:
> Hello,
> 
> does anyone know which JIT is faster - Tya or shuJIT?

http://www.tu-chemnitz.de/urz/java/news/00021.html

Ciao,
Andreas


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: server sees no body when doing HTTP POST

2001-01-29 Thread Steinar Bang

> Steinar Bang <[EMAIL PROTECTED]>:

> Platform: SuSE linux 6.2 (w/kernel version 2.2.14), Blackdown JDK 1.1.7v3

> I've been trying to write a small test program that writes a
> multipart/form-data body to an apache Tomcat servlet, using HTTP
> POST.

> What happens is that the servlet sees the headers, but not the body of 
> the message I'm trying to write.  

Seems like the line at the end of the quoted text below, is the
culprit.  If I remove it, then the body of the POSTed message is no
longer empty.

>   String boundary = "12345xyzzy";
>   URL repository = new URL("http://" + server_ + servlet_);
>   HttpURLConnection tc =
>   (HttpURLConnection)repository.openConnection();
>   tc.setDoOutput(true);
>   tc.setDoInput(true);
>   tc.setAllowUserInteraction(false);
>   tc.setRequestMethod("POST");
>   tc.setRequestProperty ("Content-Type",
>  "multipart/form-data; "
>  + "boundary=" + boundary);
>   PrintWriter out = new PrintWriter(tc.getOutputStream());
>   //PrintWriter out = new PrintWriter(System.out);
>   retval = new BufferedReader(new InputStreamReader(tc.getInputStream()));

However, if I can't do this, how can I read back the result of a POST
command...?  Hm...


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: server sees no body when doing HTTP POST

2001-01-29 Thread Steinar Bang

> Steinar Bang <[EMAIL PROTECTED]>:

> Steinar Bang <[EMAIL PROTECTED]>:
>> Platform: SuSE linux 6.2 (w/kernel version 2.2.14), Blackdown JDK 1.1.7v3

>> I've been trying to write a small test program that writes a
>> multipart/form-data body to an apache Tomcat servlet, using HTTP
>> POST.

>> What happens is that the servlet sees the headers, but not the body of 
>> the message I'm trying to write.  

> Seems like the line at the end of the quoted text below, is the
> culprit.  If I remove it, then the body of the POSTed message is no
> longer empty.

[snip!]
> However, if I can't do this, how can I read back the result of a POST
> command...?  Hm...

The answer is: create the BufferedReader _after_ we have finished
writing:



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




JMF problem with receiving streamed video, RTP related

2001-01-29 Thread Viktor Sigurd Wold Eide



I sent a bug report for JMF to http://www.blackdown.org/cgi-bin/jdk,
id = 2205. I have included the bug report below.

I would like to add that I have the same problem when using JMF for
streaming of audio over RTP.

Here is the output when when running netstat on the receiver machine.
The machine with the interface 192.168.0.1 performs the streaming on
port 7776 while the machine with interface 192.168.0.2 receives. The
receiving machine transmits a lot of messages back to the sender which
looks like RTCP Receiver Report messages when running netstat with the
-T rtcp argument (not included here). The sending of ca. 50 Receiver
Reports in a second is presumably a bug.


20:23:26.996558 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.010009 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.024760 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.038178 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.051553 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.053816 192.168.0.1. > 224.0.10.1.7776: udp 1270 [ttl 1]
20:23:27.065630 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.079002 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.092398 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.105871 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.125510 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.134982 192.168.0.1. > 224.0.10.1.7776: udp 1270 [ttl 1]
20:23:27.139352 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.152905 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.166350 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.179748 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.193177 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.207947 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.210239 192.168.0.1. > 224.0.10.1.7776: udp 1270 [ttl 1]
20:23:27.222040 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.235467 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.248909 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.294989 192.168.0.1. > 224.0.10.1.7776: udp 1270 [ttl 1]
20:23:27.362253 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.365009 192.168.0.1. > 224.0.10.1.7776: udp 1270 [ttl 1]
20:23:27.376739 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.390152 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.404827 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.418304 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.431769 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.445019 192.168.0.1. > 224.0.10.1.7776: udp 1270 [ttl 1]
20:23:27.451000 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.464669 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.478117 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.492809 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.506415 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.519904 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.522374 192.168.0.1. > 224.0.10.1.7776: udp 1270 [ttl 1]
20:23:27.534066 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.547595 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.561106 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.574567 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.589268 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.602739 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.605086 192.168.0.1. > 224.0.10.1.7776: udp 1269 [ttl 1]
20:23:27.617115 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.630739 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.685053 192.168.0.1. > 224.0.10.1.7776: udp 1270 [ttl 1]
20:23:27.744486 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.758008 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.760483 192.168.0.1. > 224.0.10.1.7776: udp 1270 [ttl 1]
20:23:27.778762 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.792243 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.805826 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.819354 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.832864 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.845023 192.168.0.1. > 224.0.10.1.7776: udp 1270 [ttl 1]
20:23:27.846887 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.860560 192.168.0.2. > 224.0.10.1.: udp 132 (DF) [ttl 1]
20:23:27.875425 192.168.0.2. > 224.0.10.1.: ud

Re: Tya vs. shuJIT

2001-01-29 Thread SHUDO Kazuyuki

Volker wrote:

> does anyone know which JIT is faster - Tya or shuJIT?

http://www.shudo.net/jit/perf/

This page shows results of performance comparisons of
Java runtimes. Applied benchmarks are SPEC JVM98,
SciMark 2.0, Linpack benchmark and Eratosthenes sieve.

Andreas wrote:

> http://www.tu-chemnitz.de/urz/java/news/00021.html

The results shown in this page are quite old.

Kazuyuki SHUDO  Happy Hacking!
  Muraoka Lab., Grad. School of Sci. & Eng., Waseda Univ.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Tya vs. shuJIT

2001-01-29 Thread David Brownell

It'd be interesting to see a current version of GCJ in those
comparisons.  GCJ 2.95.2 is listed in the shudo.net page,
but that's _extremely_ old ... I'd suggest using the 2.96 that
is distributed with RedHat 7.0, as the most current "stable"
version available.  (GCC 3.0 will have a more up-to-date
version, although still without serious optimizations.  But
that codebase is still slushing, in prep for a release.)

- Dave


- Original Message - 
From: SHUDO Kazuyuki <[EMAIL PROTECTED]>
To: Volker <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, January 29, 2001 5:46 AM
Subject: Re: Tya vs. shuJIT


> Volker wrote:
> 
> > does anyone know which JIT is faster - Tya or shuJIT?
> 
> http://www.shudo.net/jit/perf/
> 
> This page shows results of performance comparisons of
> Java runtimes. Applied benchmarks are SPEC JVM98,
> SciMark 2.0, Linpack benchmark and Eratosthenes sieve.
> 
> Andreas wrote:
> 
> > http://www.tu-chemnitz.de/urz/java/news/00021.html
> 
> The results shown in this page are quite old.
> 
> Kazuyuki SHUDO Happy Hacking!
>   Muraoka Lab., Grad. School of Sci. & Eng., Waseda Univ.
> 
> 
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: server sees no body when doing HTTP POST

2001-01-29 Thread John D. Mitchell

> "Steinar" == Steinar Bang <[EMAIL PROTECTED]> writes:
[...]
> The answer is: create the BufferedReader _after_ we have finished
> writing: 

:-) Indeed.

In general, with respect to dealing with HTTP in Java, rather than reading
all of the related RFCs and trying to implement them yourself, I strongly
suggest that people use (and enhance!) an existing HTTP client package such
as the open source HTTPClient, http://www.innovation.ch/java/HTTPClient/

Take care,
John

--
jGuru.com -- Unleash the Guru Within!
JavaWorld.com -- Share your Tips and Tricks!


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Unsubscribe java-linux

2001-01-29 Thread Todd Saskiw
Title: Unsubscribe java-linux





Unsubscribe java-linux






Unsubscribe java-linux

2001-01-29 Thread luke1101net
Title: Unsubscribe java-linux



 

   
  Unsubscribe java-linux 


Using and Building UDDI4J

2001-01-29 Thread Anuraj Singh


<>--<>


uddi4j Project

UDDI4J is a Java class library that provides an API to interact with a UDDI
(Universal Description,
Discovery and Integration) registry. The UDDI Project is a comprehensive,
open industry initiative
enabling businesses to (I) discover each other, and (II) define how they
interact over the internet
and share information in a global registry architecture. UDDI is the
building block which will enable
businesses to quickly, easily and dynamically find and transact with one
another via their preferred applications.

Complete Article
http://oss.software.ibm.com/developerworks/projects/uddi4j/?open&l=jlbd,t=gr,p=uddi4jpro


<>--<>


UDDI4J: Matchmaking for Web services
Interacting with a UDDI server

As part of its continued commitment to Web services, IBM has released
UDDI4J,
an open-source Java implementation of the Universal Discovery, Description,
and Integration protocol (UDDI). In this article, we'll discuss the basics
of UDDI,
the Java API to UDDI, and how you can use this technology to start
building,
testing, and deploying your own Web services.

Complete Article
http://www-106.ibm.com/developerworks/library/ws-uddi4j.html?dwzone=ws?open&l=jlbd,t=gr,p=uddi4j


<>--<>


SDK for Windows on Itanium

IBM® Developer Kit for Windows® on Itanium?, Java? 2 Technology Edition,
Version 1.3 Beta 2 level code
is an early version of the Java SDK ported to Windows 2000 running on
Intel's Itanium hardware.
In general, the content of this Developer Kit follows that for 32 bit
Windows as described in the
IBM Developer Kit and Runtime Environment for Windows, Java 2 Technology
Edition, Version 1.3 delivered
as part of IBM® WebSphere? Preview Technologies.

Free Download
http://www.alphaworks.ibm.com/tech/sdkonItanium?open&l=jlbd,t=gr,tech=sdkonItanium



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]