diff --git a/README.md b/README.md
index 8a8d3c6..421bf6e 100644
--- a/README.md
+++ b/README.md
@@ -19,14 +19,14 @@ For information on Siddhi and i
## Latest API Docs
-Latest API Docs is 3.0.1.
+Latest API Docs is 3.0.2.
## Features
-* websocket *(Sink)*
A Siddhi application can be configured to publish events via the Websocket transport by adding the @Sink(type = 'websocket') annotation at the top of an event stream definition.
A Siddhi application can be configured to publish events via the WebSocket transport by adding the @Sink(type = 'websocket-server') annotation at the top of an event stream definition.
A Siddhi application can be configured to receive events via the WebSocket by adding the @Source(type = 'websocket') annotation at the top of an event stream definition.
When this is defined the associated stream will receive events from the WebSocket server on the url defined in the system.
A Siddhi application can be configured to receive events via the WebSocket by adding the @Source(type = 'websocket-server') annotation at the top of an event stream definition.
A Siddhi application can be configured to publish events via the Websocket transport by adding the @Sink(type = 'websocket') annotation at the top of an event stream definition.
A Siddhi application can be configured to run as a websocket server by adding the @Sink(type = 'websocket-server') annotation at the top of an event stream definition.
A Siddhi application can be configured to receive events via the WebSocket by adding the @Source(type = 'websocket') annotation at the top of an event stream definition.
When this is defined the associated stream will receive events from the WebSocket server on the url defined in the system.
A Siddhi application can be configured to receive events via the WebSocket by adding the @Source(type = 'websocket-server') annotation at the top of an event stream definition.
A Siddhi application can be configured to publish events via the Websocket transport by adding the @Sink(type = 'websocket') annotation at the top of an event stream definition.
+ +Syntax + +``` +@sink(type="websocket", url="Name | +Description | +Default Value | +Possible Data Types | +Optional | +Dynamic | +
---|---|---|---|---|---|
url | +The URL of the remote endpoint. |
+ + | STRING | +No | +No | +
sub.protocol | +The negotiable sub-protocol if server is asking for it. |
+ null | +STRING | +Yes | +No | +
headers | +Any specific headers which need to send to the server. |
+ null | +STRING | +Yes | +No | +
idle.timeout | +Idle timeout of the connection |
+ -1 | +INT | +Yes | +No | +
truststore.path | +The file path to the location of the truststore. If a custom truststore is not specified, then the system uses the default truststore file - wso2carbon.jks in the |
+ ${carbon.home}/resources/security/client-truststore.jks | +STRING | +Yes | +No | +
truststore.password | +The password for the truststore. A custom password can be specified if required. If no custom password is specified, then the system uses |
+ wso2carbon | +STRING | +Yes | +No | +
A sink of type 'websocket' has been defined.
All events arriving at Foo stream will be sent to the url ws://localhost:8025/abc where the websocket server resides.
A Siddhi application can be configured to run as a websocket server by adding the @Sink(type = 'websocket-server') annotation at the top of an event stream definition.
+ +Syntax + +``` +@sink(type="websocket-server", host="Name | +Description | +Default Value | +Possible Data Types | +Optional | +Dynamic | +
---|---|---|---|---|---|
host | +host of the WebSocket server |
+ + | STRING | +No | +No | +
port | +port of the WebSocket server |
+ + | STRING | +No | +No | +
sub.protocol | +Sub-Protocols which are allowed by the service. |
+ null | +STRING | +Yes | +No | +
idle.timeout | +Idle timeout of the connection. If the idle.timeout = '-1' then the timer is disabled. |
+ -1 | +INT | +Yes | +No | +
tls.enabled | +This parameter specifies whether a secure connection is enabled or not. When this parameter is set to |
+ false | +BOOL | +Yes | +No | +
keystore.path | +The file path to the location of the keystore. If a custom keystore is not specified, then the system uses the default keystore file - wso2carbon.jks in the |
+ ${carbon.home}/resources/security/wso2carbon.jks | +STRING | +Yes | +No | +
keystore.password | +The password for the keystore. A custom password can be specified if required. If no custom password is specified, then the system uses |
+ wso2carbon | +STRING | +Yes | +No | +
A sink of type 'websocket-server' has been defined.
Clients can connect to ws://localhost:9025/abc. All events arriving at Foo stream will be sent to all the clients who got connected.
A Siddhi application can be configured to receive events via the WebSocket by adding the @Source(type = 'websocket') annotation at the top of an event stream definition.
When this is defined the associated stream will receive events from the WebSocket server on the url defined in the system.
Name | +Description | +Default Value | +Possible Data Types | +Optional | +Dynamic | +
---|---|---|---|---|---|
url | +The URL of the remote endpoint. |
+ + | STRING | +No | +No | +
sub.protocol | +The negotiable sub-protocol if server is asking for it. |
+ null | +STRING | +Yes | +No | +
headers | +Any specific headers which need to send to the server. |
+ null | +STRING | +Yes | +No | +
idle.timeout | +Idle timeout of the connection |
+ -1 | +INT | +Yes | +No | +
truststore.path | +The file path to the location of the truststore. If a custom truststore is not specified, then the system uses the default truststore file - wso2carbon.jks in the |
+ ${carbon.home}/resources/security/client-truststore.jks | +STRING | +Yes | +No | +
truststore.password | +The password for the truststore. A custom password can be specified if required. If no custom password is specified, then the system uses |
+ wso2carbon | +STRING | +Yes | +No | +
Under this configuration, events are received via the WebSocket server and they are passed to Foo
stream for processing.
A Siddhi application can be configured to receive events via the WebSocket by adding the @Source(type = 'websocket-server') annotation at the top of an event stream definition.
+ +Syntax + +``` +@source(type="websocket-server", host="Name | +Description | +Default Value | +Possible Data Types | +Optional | +Dynamic | +
---|---|---|---|---|---|
host | +host of the WebSocket server |
+ + | STRING | +No | +No | +
port | +port of the WebSocket server |
+ + | STRING | +No | +No | +
sub.protocol | +Sub-Protocols which are allowed by the service. |
+ null | +STRING | +Yes | +No | +
idle.timeout | +Idle timeout of the connection. If the idle.timeout = '-1' then the timer is disabled. |
+ -1 | +INT | +Yes | +No | +
tls.enabled | +This parameter specifies whether a secure connection is enabled or not. When this parameter is set to |
+ false | +BOOL | +Yes | +No | +
keystore.path | +The file path to the location of the keystore. If a custom keystore is not specified, then the system uses the default keystore file - wso2carbon.jks in the |
+ ${carbon.home}/resources/security/wso2carbon.jks | +STRING | +Yes | +No | +
keystore.password | +The password for the keystore. A custom password can be specified if required. If no custom password is specified, then the system uses |
+ wso2carbon | +STRING | +Yes | +No | +
Under this configuration, events are received via the WebSocket server and they are passed to Foo
stream for processing.
A sink of type 'websocket' has been defined.
All events arriving at Foo stream via websocket will be sent to the url ws://localhost:8025/abc.
A sink of type 'websocket' has been defined.
All events arriving at Foo stream will be sent to the url ws://localhost:8025/abc where the websocket server resides.
A Siddhi application can be configured to publish events via the WebSocket transport by adding the @Sink(type = 'websocket-server') annotation at the top of an event stream definition.
+A Siddhi application can be configured to run as a websocket server by adding the @Sink(type = 'websocket-server') annotation at the top of an event stream definition.
Syntax @@ -171,7 +171,7 @@ define stream Foo (attribute1 string, attribute2 int); define stream Foo (attribute1 string, attribute2 int); ``` -A sink of type 'websocket-server' has been defined.
All events arriving at Foo stream via websocket-server will be sent to the url ws://localhost:9025/abc.
A sink of type 'websocket-server' has been defined.
Clients can connect to ws://localhost:9025/abc. All events arriving at Foo stream will be sent to all the clients who got connected.
A Siddhi application can be configured to publish events via the Websocket transport by adding the @Sink(type = 'websocket') annotation at the top of an event stream definition.
A Siddhi application can be configured to publish events via the WebSocket transport by adding the @Sink(type = 'websocket-server') annotation at the top of an event stream definition.
A Siddhi application can be configured to receive events via the WebSocket by adding the @Source(type = 'websocket') annotation at the top of an event stream definition.
When this is defined the associated stream will receive events from the WebSocket server on the url defined in the system.
A Siddhi application can be configured to receive events via the WebSocket by adding the @Source(type = 'websocket-server') annotation at the top of an event stream definition.
A Siddhi application can be configured to publish events via the Websocket transport by adding the @Sink(type = 'websocket') annotation at the top of an event stream definition.
A Siddhi application can be configured to run as a websocket server by adding the @Sink(type = 'websocket-server') annotation at the top of an event stream definition.
A Siddhi application can be configured to receive events via the WebSocket by adding the @Source(type = 'websocket') annotation at the top of an event stream definition.
When this is defined the associated stream will receive events from the WebSocket server on the url defined in the system.
A Siddhi application can be configured to receive events via the WebSocket by adding the @Source(type = 'websocket-server') annotation at the top of an event stream definition.