using the message broker in in-memory mode. Therefore I
> think It is better not to that.
>
> WDYT?
> --
> Asanka Abeyweera
> Associate Technical Lead
> WSO2 Inc.
>
> Phone: +94 712228648 <071%20222%208648>
> Blog: a5anka.github.io
>
> <https://wso2.co
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> W.G. Gihan Anuruddha
>> Associate Technical Lead | WSO2, Inc.
>> M: +94772272595
>>
>> ___
&
log: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>
>>
>> --
>> Asanka Abeyweera
>> Associate Technical Lead
>> WSO2 Inc.
>>
>> Phone: +94 712228648 <071%20222%208648>
>> Blog: a5anka.github.io
&
tore manager.
>>> Authorized users can add permissions to groups using permission api. Each
>>> resource can have own way of handling permission. As an example in
>>> hierarchical topic scenario, if given user group has permission to top
>>> level topic, will be granted the permission to lower level topic structur
t an improvement and then proceed.
>
> On the other hand, if MariaDB has already implemented these capabilities
> on top of LevelDB, Isn't it better to use MariaDB?
>
> On Wed, Aug 16, 2017 at 2:59 PM, Pamod Sylvester <pa...@wso2.com> wrote:
>
>> I suppose we just need to adhere
t;>>> writing performances than RDBMS data repetition may not be an much of an
>>>>>> overhead in inserting data. Moreover batch operations can be used in
>>>>>> multiple insertions.
>>>>>>
>>>>>> The main purpose of using of prefixes like MESSAGE and QUEUE in keys
>>>>>> is to organize them properly. As LevelDB stores keys lexicographically
>>>>>> these prefixes will make sure that message related and queue related keys
>>>>>> are stored separately as displayed below. The following shows the keys of
>>>>>> the LevelDB store after publishing a JMS message to the broker. It can be
>>>>>> clearly seen that the keys are stored in lexicographical order.
>>>>>>
>>>>>> [image: Screenshot from 2017-08-14 19-57-13.png]
>>>>>>
>>>>>> Organize keys in such a manner also improves the efficiency of
>>>>>> traversing the keys using iterators when retrieving and deleting data. As
>>>>>> displayed in the diagram below, iterators traverse by starting from the
>>>>>> first stored key in the store. When iterator head reaches a key it can
>>>>>> either move to the next key or previous key. (similar to double
>>>>>> linked list) Hence storing related keys successively improves the
>>>>>> efficiency of traversing when retrieving and deleting data by reducing
>>>>>> the
>>>>>> seeking time.
>>>>>>
>>>>>>
>>>>>> [image: Screenshot from 2017-08-15 02-11-40.png]
>>>>>>
>>>>>>
>>>>>> Basically these are the factors and decisions which have been taken
>>>>>> in implementing this key schema. And this schema should be extended to
>>>>>> provide functionalities like storing message expiration data etc. It
>>>>>> would
>>>>>> be great to to have a feedback on the proposed schema specially regarding
>>>>>> how to reduce data repetition and improve efficiency furthermore.
>>>>>>
>>>>>> [1] https://github.com/fusesource/leveldbjni
>>>>>>
>>>>>>
>>>>>> Best Regards,
>>>>>> --
>>>>>>
>>>>>> *Wishmitha Mendis*
>>>>>>
>>>>>> *Intern - Software Engineering*
>>>>>> *WSO2*
>>>>>>
>>>>>> *Mobile : +94 777577706 <077%20757%207706>*
>>>>>>
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Architecture mailing list
>>>>>> Architecture@wso2.org
>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ___
>>>>> Architecture mailing list
>>>>> Architecture@wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Wishmitha Mendis*
>>>>
>>>> *Intern - Software Engineering*
>>>> *WSO2*
>>>>
>>>> *Mobile : +94 777577706 <+94%2077%20757%207706>*
>>>>
>>>>
>>>>
>>>> ___
>>>> Architecture mailing list
>>>> Architecture@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Asanka Abeyweera
>>> Senior Software Engineer
>>> WSO2 Inc.
>>>
>>> Phone: +94 712228648 <+94%2071%20222%208648>
>>> Blog: a5anka.github.io
>>>
>>> <https://wso2.com/signature>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Wishmitha Mendis*
>>
>> *Intern - Software Engineering*
>> *WSO2*
>>
>> *Mobile : +94 777577706 <+94%2077%20757%207706>*
>>
>>
>>
>
>
> --
> Asanka Abeyweera
> Senior Software Engineer
> WSO2 Inc.
>
> Phone: +94 712228648 <071%20222%208648>
> Blog: a5anka.github.io
>
> <https://wso2.com/signature>
>
--
*Pamod Sylvester *
*WSO2 Inc.; http://wso2.com <http://wso2.com>*
cell: +94 77 7779495
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
;>>>
>>>>>>>>>>Provide persistence by writing to hard disk in configurable
>>>>>>>>>>intervals. (snapshots : https://redis.io/topics/persistence)
>>>>>>>>>>3.
>>>>>>>&
URLs ?
>
> For an example shall we use
> /dlc/{dlc-queue-name}/queue-name/{queue-name} or
>
> /dlc/{dlc-queue-name}/{queue-name} or shall we give
>
> {queue-name} as query parameter
>
> Feedback is appreciated.
>
> Thanks,
> --
> Malaka.
> --
>
eed
> Software Engineer, WSO2 Lanka (Pvt) Ltd <http://wso2.com/>
>
> Email: riy...@wso2.com <riyafa...@cse.mrt.ac.lk>
> Website: https://riyafa.wordpress.com/ <http://riyafa.wordpress.com/>
> <http://facebook.com/riyafa.ahf>
cations required.
>>
>> Thank you,
>> Maryam
>> --
>> *Maryam Ziyad Mohamed*
>> Software Engineer | WSO2
>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>
>
>
>
> --
> *Maryam Ziyad Mohamed*
> Software Engineer | WS
ld it up as well. Shall
> we try to identify above scenarios?
>
>
> --
> Sharon David
> Software Engineer - UI/UX | WSO2 Inc
>
> +94 777 668 411 | shar...@wso2.com | http://wso2.com
>
--
*Pamod Sylvester *
*WSO2 Inc.; http://wso2.com <http://wso2.com>*
c
activemq/artemis/
> jms/client/ActiveMQJMSContext.java
> [3] https://github.com/apache/qpid-jms/blob/master/qpid-jms-
> client/src/main/java/org/apache/qpid/jms/JmsContext.java
>
> Thank you,
> Maryam
> --
> *Maryam Ziyad Mohamed*
> Software Engineer | WSO2
> [image: http://
ng the Shazni's question, In Queues, I believe we need to keep
> remain unmatched messages in the queue/DLC since it wasn't delivered
> correctly. We should deliver this message if someone interested later. WDYT
> ??
>
> Thanks,
> Madhawa
>
> On Wed, Dec 7, 2016 at 9:24 PM, Pamo
it to be extended if it's
required :)
Thanks,
Pamod
On Wednesday, December 7, 2016, Hasitha Hiranya <hasit...@wso2.com> wrote:
> Hi Pamod,
>
> On Wed, Dec 7, 2016 at 8:39 AM, Pamod Sylvester <pa...@wso2.com> wrote:
>
>> Hi Hasitha,
>>
>> Just to
7, 2016 at 3:27 AM, Pamod Sylvester <pa...@wso2.com
> <javascript:_e(%7B%7D,'cvml','pa...@wso2.com');>> wrote:
>
>> Hi Hasitha,
>>
>> An aspect i was thinking is. let's say there's a durable subscription
>> having the selector query/condition as '*groupID >
st Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Sidath Weerasinghe
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *Intern*
>>>>>>&
>
>
> Thanks & Regards,
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> ___
> Architecture mailing list
> Architecture@wso2.o
SO2 Inc.
>> Mobile : +94713068779
>>
>> <http://sanjeewamalalgoda.blogspot.com/>blog
>> :http://sanjeewamalalgoda.blogspot.com/
>> <http://sanjeewamalalgoda.blogspot.com/>
>>
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.
> blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/>
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
*Pamod Sylvester *
*WSO2 Inc.; http://wso2.com <http://wso2.com>*
cell: +94 77 7779495
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
. The Websocket frames would be further encoded into HTTP bytes message
which would make it ready to be transmitted through the wire to the
Websocket client.
[1] [Architecture] [MB] Generalizing the transport model and Revamping MQTT
transport
Thanks,
Pamod
--
*Pamod Sylvester *
*WSO2 Inc.; http://wso2
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> ====
> Srinath Perera, Ph.D.
>http://p
lly designed for MB use-case?
>
> On Thu, Mar 10, 2016 at 7:23 PM, Pamod Sylvester <pa...@wso2.com> wrote:
>
>> Hi All,
>>
>> Further to the discussion in [1], following is a design derived to revamp
>> the existing MQTT transport,
>>
>> *Goals of th
layer from core
[2] https://github.com/andsel/moquette
[3]
https://github.com/wso2/carbon-messaging/blob/master/components/src/main/java/org/wso2/carbon/messaging/CarbonTransportInitializer.java
Thanks,
Pamod
--
*Pamod Sylvester *
*WSO2 Inc.; http://wso2.com <http://wso2.com>*
cell
ge 1]
>
> Thanks,
> NuwanD.
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
&
of the referencing service
optional [1] could be a solution, but we need to understand whether there's
a better approach for this.
WDYT ?
[1]
http://docs.spring.io/osgi/docs/current/api/org/springframework/osgi/service/importer/support/Cardinality.html
Thanks,
Pamod
--
*Pamod Sylvester *
*WSO2 Inc.; http
on the possibility of addressing
the circular dependencies. Ideally i do agree the core should be totally
independent of protocol logic.
Thanks,
Pamod
On Tue, Feb 9, 2016 at 4:36 PM, Selvaratnam Uthaiyashankar <shan...@wso2.com
> wrote:
>
>
> On Tuesday, February 9, 2016, Pamod Sylvester
asis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html
>> [2] http://eprints.port.ac.uk/15538/1/oauth_mqtt3.pdf
>> [3] http://www.hivemq.com/blog/mqtt-security-fundamentals-oauth-2-0-mqtt
>> [4]
>> https://github.com/ayyoob/extensions/tree/master/messagebroker-extensions
>> *Ayyoob Hamza*
>> *Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
>>
>
>
>
> --
> Paul Fremantle
> Co-Founder, WSO2
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
>
>
--
*Pamod Sylvester *
*WSO2 Inc.; http://wso2.com <http://wso2.com>*
cell: +94 77 7779495
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
on.blogspot.com>
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>
, 2015 at 11:43 AM, Asitha Nanayakkara asi...@wso2.com wrote:
Hi Pamod,
On Mon, Jun 8, 2015 at 10:43 AM, Pamod Sylvester pa...@wso2.com wrote:
Hi Sasikala,
As discussed offline, let's try to figure out the reason for the
ruminant. If the reason is due to the load (i.e db latency to delete
**DistributedStoreConnector
- Default h2 as db*100,00022008002000*InMemoryConnector*
100,00028721225.22200
Note : the comparison was done having the MB executed in stand-alone mode.
The messages were sent/received with QoS level 0.
Please do comment if i've missed out on anything. WDYT ?
Thanks,
Pamod
--
Pamod
subscriptions are QOS0, then skip
writing to the disk).
2. Too late to do the change now, lets do it for the next release.
--Srinath
On Thu, May 14, 2015 at 9:05 AM, Pamod Sylvester pa...@wso2.com wrote:
Hi Hasitha,
+1 Srinath too suggested on same.
Thanks,
Pamod
On Thu, May 14, 2015 at 2
?
Thanks
On Wed, May 13, 2015 at 4:35 AM, Pamod Sylvester pa...@wso2.com wrote:
Hi All,
The following changes were made to the MQTT architecture in order to
achieve a more flexible/extensible design. The details are as follows,
*Design *
The goal is to allow flexibility to define distribution
message.
So how should we handle the PUBACK sent from the broker and avoid the
client retries?
Thanks,
Akalanka
On Fri, Apr 17, 2015 at 11:33 AM, Pamod Sylvester pa...@wso2.com wrote:
Hi Akalanka,
One way i could think of as a solution would be to,
1) When the publisher/subscriber
your thoughts on this.
--
Asanka Abeyweera
Software Engineer
WSO2 Inc.
Phone: +94 712228648
Blog: a5anka.github.io
--
*Pamod Sylvester *
*Senior Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
Silva
Software Engineer
Mobile : 0772037426
Blog: http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )
--
*Pamod Sylvester *
*Senior Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77
...@wso2.com wrote:
What are the properties we need to have for mqtt?
On Thu, Nov 13, 2014 at 9:22 PM, Pamod Sylvester pa...@wso2.com wrote:
Hi HasithaA,
For MQTT since the transport properties etc will be included in the
broker.xml we might not need a separate config (mqtt-config.xml) IMO
this is my reading of the spec.
Paul
On 23 October 2014 11:17, Pamod Sylvester pa...@wso2.com wrote:
Hi All,
The current MB kernal architecture, complies to a model which takes each
of the messages published through the store before delivering to the
subscribers. Comparing against AMQP
or
should we stick with shipping MQTT having only QOS 1 and support levels 0,2
for the next release.
WDYT ?
Thanks,
Pamod
--
*Pamod Sylvester *
*Senior Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
*Pamod Sylvester *
*Senior
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
*Pamod Sylvester *
*Senior Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
___
Architecture mailing list
Architecture
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
*Pamod Sylvester *
* Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
___
Architecture mailing list
.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
*Pamod Sylvester *
* Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
failures, also will be looking at the possibilities to reduce the latency
of the response time so that the tests will be positive for the default
parameters.
Thanks,
Pamod
On Sat, Mar 8, 2014 at 4:58 PM, Pamod Sylvester pa...@wso2.com wrote:
Hi Paul,
+1 to reflect the changes back
Yes. They are Junit test cases. We could integrate them.
Thanks,
Pamod
On Mon, Mar 10, 2014 at 2:15 PM, Srinath Perera srin...@wso2.com wrote:
ah OK. Can we get the introp tests integrated with our product or
integration tests?
On Mon, Mar 10, 2014 at 2:03 PM, Pamod Sylvester pa...@wso2
the
Moquette group this is a valuable change/addition.
Is there any chance of doing an interop test with a beta on the 17th
March at EclipseCon? I'll be at the interop day.
Paul
On 8 March 2014 05:36, Pamod Sylvester pa...@wso2.com wrote:
Hi Samisa,
Yes we did changes which are local to the Moquette
/
--
*Pamod Sylvester *
* Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
attachment: MQTT Message Flow.png___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org
.
Thanks,
Pamod
On Sat, Mar 8, 2014 at 10:35 AM, Samisa Abeysinghe sam...@wso2.com wrote:
On Sat, Mar 8, 2014 at 10:00 AM, Pamod Sylvester pa...@wso2.com wrote:
Hi All,
The following is the status of the MQTT Moquette library integration with
MB 3.0.0,
~ Library was revamped to fit
46 matches
Mail list logo
