File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Beginning Java and the fly likes Difference between and API in SDK1.4 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Java » Beginning Java
Bookmark "Difference between and API in SDK1.4" Watch "Difference between and API in SDK1.4" New topic

Difference between and API in SDK1.4

Chandhrasekar Saravanan
Ranch Hand

Joined: Jun 16, 2002
Posts: 57
I like to know the major difference between
the and api in sdk1.4 .
what are the applications of
i know , is used for making simple
tcp/ip servers and clients. is is
used in creating servers and clients which allows xml processing.
why has sun included this api in their new
thanks in advance
Chandhrasekar Saravanan
Gregg Bolinger
GenRocket Founder
Ranch Hand

Joined: Jul 11, 2001
Posts: 15302

I think that the major thing about is that it contains the SSL package for secure sockets. only provides normal socket operation. And* does not provide the same things that provides. So one is not to take place of the other.

GenRocket - Experts at Building Test Data
Karl Laird
Ranch Hand

Joined: Jul 14, 2001
Posts: 67
The primary difference is that javax packages have not been accepted into the main code base of java yet and are still considered 'eXperimental'. This is not to say they are Beta but that their inclusion as core packages is not confirmed. If you look back through the history of the java releases (1.1, 1.2, etc) at one stage the swing classes were all javax.swing rather than java.swing but these were then made part of the 'official' code base. Hence the main difference is not to do with the actual functions but where the support for the packages lies

The Eagle sneers at the Peacock<p>Systems Administrator<br />OrderWare Solutions Ltd<br /><a href="" target="_blank" rel="nofollow"></a>
Dirk Schreckmann

Joined: Dec 10, 2001
Posts: 7023
javax packages are extension packages not experimental packages. Also, the Swing package is still referenced by javax.swing and there is no package called java.swing .
From The Java Extensions FAQ:
How will standard extensions be named?
Standard extensions will have names in the javax.* namespace. Exceptions will be allowed on a case-by-case basis, as for example, when necessary because of open standards. However, just because a package name begins with javax does not guarantee that that package is an extension rather than a part of the core platform. The Swing packages have names beginning with javax indicating that they were non-core extensions prior to version 1.2 of the platform. They are part of the core 1.2 platform even though they are in the javax.* namespace.

[How To Ask Good Questions] [JavaRanch FAQ Wiki] [JavaRanch Radio]
Jim Yingst

Joined: Jan 30, 2000
Posts: 18671
In other words, javax indicates that when the package was first named, it was considered an optional extension, not part of the core. However its status might have changed later, and since Sun would prefer not to force people to change all their import statements to get code to work, they keep the original package name.

"I'm not back." - Bill Harding, Twister
I agree. Here's the link:
subject: Difference between and API in SDK1.4
jQuery in Action, 3rd edition