Re: cluster computing

[Dain Sundstrom]

Myriam,

I strongly suggest you do not use RMI for clustering.  Actually, basic 
RMI over JRMP (Java Remote Method Protocol?) is incredibility 
inefficient.  Most EJB servers support it for compatibility reasons, 
but use a custom protocol by default.  The biggest problem with using 
RMI and any RPC protocol for clustering is they are inherently point to 
point when you really want to use one to many channels.  For 
clustering, I suggest you use JavaGroups, by Bela Ban 
(www.javagroups.com).  JavaGroups is specifically designed to support 
group communication (i.e., clusters), and by default uses a reliable 
multicast protocol stack.  JavaGroups is the basis of JBoss clustering, 
and Bela is a JBoss Group member.  Bela is currently working on a 
distributed caching system.  Anyway, I suggest you send an email to 
Bela.

Oh ya, we (The JBoss Group) have had a lot of researchers from national 
labs at our trainings doing work on grid computing systems based on 
JBoss if that is what you are doing.

-dain

/**
 * @name Dain Sundstrom
 * @titleAuthor CMP on JBoss
 * @company  The JBoss Group, LLC.
 */


On Wednesday, January 1, 2003, at 03:11 PM, Myriam Abramson wrote:


Hi!

I am studying RMI and it seems to me that it's a great tool for
cluster computing. How many of you actually use it on a linux cluster?
I'm asking because where I work, they adamantly want to use the MPI
protocol with c++ going as far as converting java code!

TIA and HNY!

   myriam


--
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]

file.encoding change between jdk 1.3.1 and 1.4.1

[Joseph Shraibman]

I have code to create a Multipart like this:

MimeMultipart mm = new MimeMultipart("alternative");
BodyPart bp = new MimeBodyPart() ;
bp.setText(text);
mm.addBodyPart(bp);
bp = new MimeBodyPart() ; //reset variable for html part
bp.setContent(html,"text/html");
mm.addBodyPart(bp);

Under java 1.3.1 this generated mail that had this for the html multipart:

--=_Part_2_6220608.1041458193261
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

When I upgraded to 1.4.1 it now looks like this:
--=_Part_21_20566889.1041555012620
Content-Type: text/html; charset=ANSI_X3.4-1968
Content-Transfer-Encoding: quoted-printable

This charset=ANSI_X3.4-1968 is causing problems when netscape reads the mail. It appears 
that file.encoding changed between versions. Does anyone know why?



--
Joseph Shraibman
[EMAIL PROTECTED]
Increase signal to noise ratio.  http://xis.xtenit.com


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

Re: [JAVAMAIL-INTEREST] file.encoding change between jdk 1.3.1 and1.4.1

[Joseph Shraibman]

BTW can I get a survey of what your file.encodings and systems are?  A quick way to find 
out if you have beanshell in your classpath:

echo "System.out.println(System.getProperty(\"file.encoding\"));" | java bsh.Interpreter

The system where I had this problem is a redhat 6.x system. On a rh 8.0 that used to be a 
7.2 it is ISO-8859-1, and on a system that always was 8.0 it is UTF-8

Joseph Shraibman wrote:
I have code to create a Multipart like this:

MimeMultipart mm = new MimeMultipart("alternative");
BodyPart bp = new MimeBodyPart() ;
bp.setText(text);
mm.addBodyPart(bp);
bp = new MimeBodyPart() ; //reset variable for html part
bp.setContent(html,"text/html");
mm.addBodyPart(bp);

Under java 1.3.1 this generated mail that had this for the html multipart:

--=_Part_2_6220608.1041458193261
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

When I upgraded to 1.4.1 it now looks like this:
--=_Part_21_20566889.1041555012620
Content-Type: text/html; charset=ANSI_X3.4-1968
Content-Transfer-Encoding: quoted-printable

This charset=ANSI_X3.4-1968 is causing problems when netscape reads the 
mail. It appears
that file.encoding changed between versions. Does anyone know why?




--
Joseph Shraibman
[EMAIL PROTECTED]
Increase signal to noise ratio.  http://xis.xtenit.com


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