hi folks, I was just looking at java.net.* package this afternoon. in fact, there is a tutorial about how to create URL, parse URL, read and write from URL. but i wondering when do we use these in real world. could please someone give some scenario or situation where we make use of these URL stuffs? Suppose, what is the point of reading, let's say, www.yahoo.com? or even what is the point of parsing a particular URL let's say, www.yahoo.com? please give me some insight into the need of these URL capabilities. thanks.
I use URLs for some pretty pedestrian stuff ... downloading files from web servers, checking to see if web servers are running and giving correct results. You could make a servlet read the content off Yahoo and write it out in the middle of your own HTML, but that would be unsanitary and antisocial. I think some portal technologies do that to put external content into tightly controlled frames. Afterthought: One can create web services to work through normal GET and POST. Then you could use normal URL - or even a browser - to call them. Some of the very inventors of HTTP claim that GET and POST are all we need in the world, no SOAP or fancy schmancy web services engines. Google for "REST architecture" for more details. [ August 05, 2003: Message edited by: Stan James ]
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi