Line | |
---|
1 | Greenstone 3 now includes support for client-side XSLT, i.e. the
|
---|
2 | user's web browser is responsible for converting the raw XML message
|
---|
3 | returned by the web server into a web page (using the XSL file also
|
---|
4 | returned from the web server). The seeds of this idea came from work
|
---|
5 | on supporting Greenstone installed on an Android device. Other work
|
---|
6 | done at this time to make the Greenstone 3 server run more efficiently
|
---|
7 | was profiling the code for the most expensive methods, resulting in
|
---|
8 | principally changes in how strings were handled.
|
---|
9 |
|
---|
10 |
|
---|
11 | More specifically the main modifications were:
|
---|
12 |
|
---|
13 | * The use of Apache Commons StringUtils class for text replacement and
|
---|
14 | splitting;
|
---|
15 |
|
---|
16 | * The use of StringUtils.contains over the *.text.* regular expression;
|
---|
17 |
|
---|
18 | * Plus: client-side XSLT support.
|
---|
19 |
|
---|
20 | Note that the XML Texts collection had to be modified in certain areas
|
---|
21 | due to it using four XSL overrides in its transform directory. This
|
---|
22 | may or may not be necessary depending on the XSL overrides in place
|
---|
23 | for other collections. For an example of this, see the
|
---|
24 | about-clientside.xsl file in the gberg collection.
|
---|
25 |
|
---|
26 | Steven McTainsh
|
---|
27 | February 2011
|
---|
28 |
|
---|
Note:
See
TracBrowser
for help on using the repository browser.