A Directory object contains a string representation of a URL
![]() | Directory () Default constructor |
![]() | Directory (const string& url) |
![]() | ~Directory () |
![]() | operator= (const Directory& dir) |
![]() | toString () const |
![]() | operator== (const Directory& dir) const |
![]() | parseDir (URL& url) const |
![]() | writeObject (AkentiOutputStream& drain) const |
![]() | readObject (AkentiInputStream& source) |
![]() | toXML (DOMElement* dir) const Populates the XML element dir from this Directory |
![]() | fromXML (const DOMElement* dir) Initializes this Directory from the XML element dir |
![]() | paramString () const Used for debugging |
A Directory object contains a string representation of a URL. It was introduced in addition to the URL class for two reasons. 1) Policy and UseConditition Certificates contain urls pointing to directories in which to search for other certificates. Since these urls are contained in the signable part of a certificate, we must maintain the exact string representation of the url. Example: "http://hostname:8080/filename "http://hostname:80/filename/ "http://hostname/filename/ The URL class can parse this but the URL.toString() will not return the exact string. Should it? 2) A URLHandler may not be installed. And not being able to parse a particular url should not trigger an exception when reading a certificate. 3) A Directory object provides us a cleaner and a more flexible solution for the future.
Directory(const string& url)
~Directory()
void operator=(const Directory& dir)
const string& toString() const
bool operator==(const Directory& dir) const
bool parseDir(URL& url) const
void writeObject(AkentiOutputStream& drain) const
void readObject(AkentiInputStream& source)
void toXML(DOMElement* dir) const
void fromXML(const DOMElement* dir)
string paramString() const
alphabetic index hierarchy of classes
this page has been generated automatically by doc++
(c)opyright by Malte Zöckler, Roland Wunderling
contact: doc++@zib.de