It is the Java language binding for the Subversion API.
Here are some good links:
Saturday, December 6, 2008
DOCTYPE Declaration
• Notation:
Using System identifier: The system identifier "hello.dtd" gives the address (a URI reference) of a DTD for the document. Greeting is the name of the root element of the XML document as it is defined in the DTD
<!DOCTYPE greeting SYSTEM "hello.dtd">
Using Public Identifier:
<!DOCTYPE greeting PUBLIC "Public Identifier" "hello.dtd">
Using Inline (Internal Subset) definition: Allows to contain Markup Declarations in the XML Document
<!DOCTYPE test [<!ELEMENT test (#PCDATA)> ]>
References:
Using System identifier: The system identifier "hello.dtd" gives the address (a URI reference) of a DTD for the document. Greeting is the name of the root element of the XML document as it is defined in the DTD
<!DOCTYPE greeting SYSTEM "hello.dtd">
Using Public Identifier:
<!DOCTYPE greeting PUBLIC "Public Identifier" "hello.dtd">
Using Inline (Internal Subset) definition: Allows to contain Markup Declarations in the XML Document
<!DOCTYPE test [<!ELEMENT test (#PCDATA)> ]>
References:
Controlling the DOCTYPE and XML Declaration
Drop the <!DOCTYPE >The Escape Characters
Sunday, November 16, 2008
Wednesday, August 6, 2008
Usability in Apache web server
The term Usability is used to reflect the friendliness and ease of use of a system. We are as developers have to give more attention to it. Many smart systems were forgotten because they did not take care of several usability factors such as ease of use, ease of remembering, ease of learning and task support.
We are as developers use each others code and integrate each others systems. This makes us as users of each others work and we need to put more attention to such systems' usability.
Apache web server is an example of a system that is used widely in the open source community. Installing it and configuring it is far from being friendly or usable. I am saying because I suffered from many hours of frustration trying to trace the cause of Apache failure after adding new virtual site. It turned in the end a spelling mistake in the path to the log directory!
The story started by installing Apache on Windows XP, by following a grate tutorial from http://wamp.corephp.co.uk/step_01.php. The pain started when I edited a configuration file (httpd-vhosts.conf) to add a new virtual site and I had to restart Apache to see the effects of my changes. I used Apache Monitor to start it and it wouldn't start.
I tried starting it from the command prompt by calling "httpd.exe", which means "apache.exe"!!! With no luck, it was closing silently. All what I was looking for is a descriptive messages about what went wrong. After several trials and searching the web, I found an indirect clue in Apache web site (http://httpd.apache.org/docs/2.0/platform/windows.html). It pointed me to an error log file named (error.log) inside Apache installation folder. There I found the devil;
(OS 3)The system cannot find the path specified. : httpd.exe: could not open error log file D:/www/ittrade.dev/log/error_log.txt.Unable to open logs
The path to log folder of my site has spelling mistake, it is
D:/www/ittrade.dev/log/error_log.txt in the configuration file while it was D:/www/ittrade.dev/logs/error_log.txt in the folder structure!!!
I am just wondering why it is made in this way? Was it difficult to show this error message to the standard output instead of all the silly messages showed in figures 1 & 2 or even worse when the httpd closed silently without any hint? Was it difficult to put another option to httpd that says dump/show error message(s) to the screen? Although it want be that helpful if the user has to go that far.
I believe if the developers of Apache have paid more attention to usability their job will be very much more appreciated that just pumping a system with more functionality, that many want use at all.
We are as developers use each others code and integrate each others systems. This makes us as users of each others work and we need to put more attention to such systems' usability.
Apache web server is an example of a system that is used widely in the open source community. Installing it and configuring it is far from being friendly or usable. I am saying because I suffered from many hours of frustration trying to trace the cause of Apache failure after adding new virtual site. It turned in the end a spelling mistake in the path to the log directory!
The story started by installing Apache on Windows XP, by following a grate tutorial from http://wamp.corephp.co.uk/step_01.php. The pain started when I edited a configuration file (httpd-vhosts.conf) to add a new virtual site and I had to restart Apache to see the effects of my changes. I used Apache Monitor to start it and it wouldn't start.
I got the following error message as shown in figure #1. Trying to start the server from "Services" did not help at all. See Figure #2. | ![]() Figure # 1 |
Figure#2 |
I tried starting it from the command prompt by calling "httpd.exe", which means "apache.exe"!!! With no luck, it was closing silently. All what I was looking for is a descriptive messages about what went wrong. After several trials and searching the web, I found an indirect clue in Apache web site (http://httpd.apache.org/docs/2.0/platform/windows.html). It pointed me to an error log file named (error.log) inside Apache installation folder. There I found the devil;
(OS 3)The system cannot find the path specified. : httpd.exe: could not open error log file D:/www/ittrade.dev/log/error_log.txt.Unable to open logs
The path to log folder of my site has spelling mistake, it is
D:/www/ittrade.dev/log/error_log.txt in the configuration file while it was D:/www/ittrade.dev/logs/error_log.txt in the folder structure!!!
I am just wondering why it is made in this way? Was it difficult to show this error message to the standard output instead of all the silly messages showed in figures 1 & 2 or even worse when the httpd closed silently without any hint? Was it difficult to put another option to httpd that says dump/show error message(s) to the screen? Although it want be that helpful if the user has to go that far.
I believe if the developers of Apache have paid more attention to usability their job will be very much more appreciated that just pumping a system with more functionality, that many want use at all.
Subscribe to:
Posts (Atom)