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, MQTT QOS 2 is dependent on publisher
side acknowledgments, where the publisher should be notified at a time
Hi all,
Problem
Currently in App Factory if Jenkins is down or unavailable when we are
creating a branch the relevant Jenkins job is not created for that
particular branch. Hence auto build and auto deploy does not work
(obviously). Even after Jenkins is recovered subsequent requests for builds
Hi Gayan,
What happens if he hits Deploy?
thanks,
dimuthu
On Thu, Oct 23, 2014 at 4:59 PM, Gayan Dhanushka gay...@wso2.com wrote:
Hi all,
Problem
Currently in App Factory if Jenkins is down or unavailable when we are
creating a branch the relevant Jenkins job is not created for that
*Rationale : *
According to AMQP spec 0_9_1 : Once purged, We need to remove all messages
which are not awaiting acknowledgement from the given queue. [1]
*Requirements in terms of MB 3.0.0 architecture : *
Once a queue purge is requested from UI console (queue-browse page), all
messages
Hi Damith,
When you say, user provides his Geo stationary position, how is the Geo
stationary position/entering the Geo-fence captured? Is it through some GPS
enabled device? If so, when setting the radius for the geo-fence, GPS
fluctuation has to be considered, in the client side. Are you
Thanks Dakshika for pointing this out
On Thu, Oct 23, 2014 at 9:19 AM, Dakshika Jayathilaka daksh...@wso2.com
wrote:
AFAIK your approach is not good. Font Awesome is third party library
that we are using. Also we are not tracking or maintaining any fork on it.
If you change CSS, other users
