On 05/10/2013 03:19 PM, Martin Kletzander wrote:
> On 04/30/2013 06:21 PM, Eric Blake wrote:
>> On 04/30/2013 09:18 AM, John Ferlan wrote:
>>> On 04/30/2013 10:42 AM, Martin Kletzander wrote:
Adding support for new attribute 'websocket' in the ''
element, the attribute value is the port t
On 04/30/2013 06:21 PM, Eric Blake wrote:
> On 04/30/2013 09:18 AM, John Ferlan wrote:
>> On 04/30/2013 10:42 AM, Martin Kletzander wrote:
>>> Adding support for new attribute 'websocket' in the ''
>>> element, the attribute value is the port to listen on with '-1'
>>> meaning auto-allocation, '0'
On 04/30/2013 06:21 PM, Eric Blake wrote:
> On 04/30/2013 09:18 AM, John Ferlan wrote:
>> On 04/30/2013 10:42 AM, Martin Kletzander wrote:
>>> Adding support for new attribute 'websocket' in the ''
>>> element, the attribute value is the port to listen on with '-1'
>>> meaning auto-allocation, '0'
On 04/30/2013 09:18 AM, John Ferlan wrote:
> On 04/30/2013 10:42 AM, Martin Kletzander wrote:
>> Adding support for new attribute 'websocket' in the ''
>> element, the attribute value is the port to listen on with '-1'
>> meaning auto-allocation, '0' meaning no websockets.
>>
>> Signed-off-by: Mart
On 04/30/2013 10:42 AM, Martin Kletzander wrote:
> Adding support for new attribute 'websocket' in the ''
> element, the attribute value is the port to listen on with '-1'
> meaning auto-allocation, '0' meaning no websockets.
>
> Signed-off-by: Martin Kletzander
> ---
> docs/formatdomain.html.in
Adding support for new attribute 'websocket' in the ''
element, the attribute value is the port to listen on with '-1'
meaning auto-allocation, '0' meaning no websockets.
Signed-off-by: Martin Kletzander
---
docs/formatdomain.html.in | 5 +
docs/schemas/domaincommon.rng | 5 +
src/
