Last updated at 4:12 pm UTC on 17 January 2006
The Network-Url package provides code for working with URL's. It allows them to be parsed from strings, including the parsing of "relative" URL's as used in HTML.
Too see URL's in action, try the following code:
'http://www.squeak.org' asUrl retrieveContents
(See Packages Team)
Okay, so how to packagize this?
- scan for things that should not be in the category
- move them to "orphaned" (or to a new package?)
- STOP until the packaging team moves to the next step.
- scan for dependencies, using Dan and Daniel's tools
- find stray methods that are in other packages
- ?? post a PackageInfo ??
1. Scanning for things that should not be there
UrlArgumentList is an unused class.
Authorizers is specific to HTTP, and should be moved to some HTTP package.
MswURL is long obsolete; it may as well be deleted.
MIMEDocument is questionable, but where else should it live? It is part of the general WWW infrastructure of Squeak.
The rest of the classes seem fine.
2. Moving to Orphan
(nothing done here yet)
- HTTP requester
- FTP client
- MailSender app registry
Network-Url is needed by:
(don't know yet)
These dependencies should be broken down by using registries. Common schemes (HTTP, mail, ftp) should have a registry per scheme of code that handles that scheme. Additionally, it should be possible to register new schemes.
4. Stray Methods
- anything else?