header

Client - Server Protocol

This demo exercises the communication between the client and the server.

Data size of parameters

Some browsers (Firefox in particular) had (or have) problems with large text nodes in XML. The next examples show replacements with large and small datasets.

1. Small dataset
2. Large dataset

Currently kss.core treats non-HTML commands differently from others. The following examples show why I think this to be a mistake.

1. Small attribute
2. Large attribute

XML escaping

Since the response message is a XML document it should obey the escaping rules of XML.

The ampersand character (&) and the left angle bracket (<) MUST NOT appear in their literal form, except when used as markup delimiters, or within a comment, a processing instruction, or a CDATA section. If they are needed elsewhere, they MUST be escaped using either numeric character references or the strings "&amp;" and "&lt;" respectively. The right angle bracket (>) may be represented using the string "&gt;", and MUST, for compatibility, be escaped using either "&gt;" or a character reference when it appears in the string "]]>" in content, when that string is not marking the end of a CDATA section.

1. Command with an &
2. Command with a <
3. Command with a >
4. Command with ]]> in a CDATA block

Currently kss.core treats non-HTML commands differently from others. These commands demonstrate if the system works ok with attributes.

1. Command with an &
2. Command with a <
3. Command with a >
4. Command with ]]>

Named entities

Named entities should work. The next example demonstrates that the server can send data with named entities.

1. Command with an à
2. Command with a é