Exception delivering message (Mail1345880665225-8-to-gmail.com) - [EOF]
One common myth about PTR records is that they are created for domain names and your domain has to have one to make sure your mail will not be rejected by other mail servers.
SENDING message from red@localhost to firstname.lastname@example.org
DEBUG: getProvider() returning javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]
DEBUG SMTP: useEhlo true, useAuth false
DEBUG SMTP: trying to connect to host "localhost", port 25, isSSL false
220 Desktop SMTP Server (JAMES SMTP Server 2.3.2) ready Sun, 5 Aug 2012 01:35:18 +0300 (EEST)
DEBUG SMTP: connected to host "localhost", port: 25
250-Desktop Hello Desktop (localhost [127.0.0.1])
DEBUG SMTP: Found extension "PIPELINING", arg ""
DEBUG SMTP: Found extension "ENHANCEDSTATUSCODES", arg ""
DEBUG SMTP: use8bit false
250 2.1.0 Sender <red@localhost> OK
250 2.1.5 Recipient <email@example.com> OK
DEBUG SMTP: Verified Addresses
DEBUG SMTP: firstname.lastname@example.org
354 Ok Send data ending with <CRLF>.<CRLF>
Subject: Testing blue from red
Content-Type: text/plain; charset=us-ascii
This is a test message
250 2.6.0 Message received
221 2.0.0 Desktop Service closing transmission channel
Anytime you find yourself writing code of the form "if the object is of type T1, then do something, but if it's of type T2, then do something else," slap yourself.
Jeff Verdegan wrote:
Tudor Raneti wrote:
This way, I handle the casts myself (there's no compile time casts occuring in Java AFAIK though compile time checks are made), but being specific should yield a slight performance boost if JIT cooperates?
How do you figure?
Dennis Deems wrote:
Tudor Raneti wrote:RTTI ... HQL ... ISP ... JIT
Please spell out words instead of using abbreviations like this. There may be readers of the forum who are not familiar with them.
Even *if* this works
the boost in performance would be so incredibly marginal that you would never notice any difference.
You're performing premature nano optimizations, which half of the time won't work out as you hoped.
after the compiler has performed type checking
In C++, the classic cast "(Shape)" does not perform RTTI. It simply tells the compiler to treat the object as the new type. In Java, which does perform the type check, this cast is often called a "type-safe downcast."