The Artima Developer Community
Sponsored Link

Java Answers Forum
one more Question

4 replies on 1 page. Most recent reply: Mar 23, 2005 1:27 PM by Jonathan Tang

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 4 replies on 1 page
park jung gyu

Posts: 4
Nickname: dalantpark
Registered: Mar, 2005

one more Question Posted: Mar 22, 2005 10:35 PM
Reply to this message Reply
Advertisement
SocksSocketImpl, PainSocketImpl, SocketInputStream ...the others

I now know they don't exist in Java API Document.

Why hiding?

It's Source Security Promblem? or ...


Matthias Neumair

Posts: 660
Nickname: neumi
Registered: Sep, 2003

Re: one more Question Posted: Mar 22, 2005 10:55 PM
Reply to this message Reply
Download the 1.5 API.

You will find the description in there.

Don't know if it als is in the 1.4 API or the online API.

Amol Brid

Posts: 43
Nickname: amolbrid
Registered: Feb, 2004

Re: one more Question Posted: Mar 23, 2005 4:50 AM
Reply to this message Reply
Hi,

These classes are not public and i think java doc is only for public and protected scope.

Don't know the reason why they want to hide these from developer.

Regards,
Amol Brid.

Matthias Neumair

Posts: 660
Nickname: neumi
Registered: Sep, 2003

Re: one more Question Posted: Mar 23, 2005 6:22 AM
Reply to this message Reply
My fault. I did not read carefully enough.

As far as I now, the javadoc utility does not generate API documentation for private classes, because there is just no need to do it.

Jonathan Tang

Posts: 3
Nickname: jdtang
Registered: Jan, 2005

Re: one more Question Posted: Mar 23, 2005 1:27 PM
Reply to this message Reply
> These classes are not public and i think java doc is only
> for public and protected scope.
>
> Don't know the reason why they want to hide these from
> developer.

Because every time you release a class for public access, you make a commitment to support it, and more importantly, to keep supporting it. Making those classes part of the public API would have committed Sun to never changing them, because doing so would break legacy code.

In general, library designers should make as little public as possible. Library users should never use undocumented code. If you do use SocksSocketImpl, PlainSocketImply, etc, you can expect them to break in the next release of Java, as Sun continues to improve the internals. (Assuming you even could, which Java should prevent unless you muck around with the source files.)

Flat View: This topic has 4 replies on 1 page
Topic: selection list Previous Topic   Next Topic Topic: apcs kid in need of helpxor

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use