IPv4 Address. . . . . . . . . . . : 10.0.215.69
Henry Wong wrote:
The core java library has a java.net.InetAddress class, which can be used to get the network information. There is no need for the application to parse the "ipconfig" output.
Henry
Sometimes the only way things ever got fixed is because people became uncomfortable.
Paul Clapham wrote:I'm sort of surprised that your library terminals let you access the command line, but anyway, my question is what's the purpose of this question? I don't suppose you plan to run a server on the library's system, so what are you getting at here?
Paul Clapham wrote:And by the way you don't need to know the IP address of the server when you try to connect to it, knowing the computer name is sufficient.
The nice thing about Standards is that there are so many to choose from!
Paul Clapham wrote:And by the way you don't need to know the IP address of the server when you try to connect to it, knowing the computer name is sufficient.
Eddie Vanda wrote:I find in my Uni I do not need admin access to run java programs, even ones with server sockets
Sometimes the only way things ever got fixed is because people became uncomfortable.
Kevin Simonson wrote:Does that answer your question?
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
Paul Clapham wrote:Not really. You're saying you plan to write an application which you will install on the library's system?
Winston Gutkowski wrote:
Kevin Simonson wrote:Does that answer your question?
Yes, but even if you can (or would want) to do it, your design assumes that every terminal in the library is managed by a single server. Now that may well be the case for your library, but it certainly isn't for all.
Winston Gutkowski wrote:And that makes your design "brittle".
Kevin Simonson wrote:
Winston Gutkowski wrote:
Yes, but even if you can (or would want) to do it, your design assumes that every terminal in the library is managed by a single server. Now that may well be the case for your library, but it certainly isn't for all.
Are you saying that I can only open up a socket between programs run on two terminals if those terminals are managed by a single server?
The nice thing about Standards is that there are so many to choose from!
Eddie Vanda wrote:
All that assumes they are on the same subnet and that the router lets requests through locally for port 80 and that the timeout is reasonably short.
Henry Wong wrote:I highly doubt that the library system administrators would disable the firewall.
Be reasonable. You can't destroy everything. Where would you sit? How would you read a tiny ad?
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
|