Hi,
Visual data mapper currently operates by taking two avro schemas for input
and output. Considering the fact that end users are not supposed to write
avro schema by themselves, we have decided to provide a UI to manually
build the schema of input and output. This will basically extend the
Hi All,
We are changing the current tenant model with a flat hierarchy in the
cloud, where we keep the email address as the user name.
In this model, the logged in user will be am...@wso2.com@abc.com, where my
domain name will be abc.com and user name will be am...@wso2.com
This introduce couple
Hi Gayan,
Please see comments inline.
On 9 Apr 2014 15:10, Gayan Yalpathwala gay...@wso2.com wrote:
Hi,
Visual data mapper currently operates by taking two avro schemas for
input and output. Considering the fact that end users are not supposed to
write avro schema by themselves, we have
Hi Harshana
Yes it is yet another option and we have tried this tool and it has some
issues with namespaces and also it generates separate files for each of
complex datatypes. If we use this i think we need to improve this and fix
the above issues.
Thanks
On Wed, Apr 9, 2014 at 5:48 PM,
Hi,
Requirement-
Currently all the below types of statistics shown in one page of
APIPublisher.
1) Overall API Usage
2) API Response Times
3) API Last Access Times
4) API Usage from Resource Path
5) API Usage by user
6) API Usage from Destination
7) Faulty invocations
When the published stats
If we separate out, the Dashboard aspect is lost, right?
Thanks,
Samisa...
Samisa Abeysinghe
Vice President Developer Evangelism
WSO2 Inc.
http://wso2.com
On Wed, Apr 9, 2014 at 6:51 PM, Lalaji Sureshika lal...@wso2.com wrote:
Hi,
Requirement-
Currently all the below types of
Hi Dilshan
What I meant is the following
tenantDomain = userName.substring(userName.lastIndexOf('@') + 1);
Since we are sure that domain name cannot contain @ taking lastIndexOf is
enough and safe rather than writing a regular expression to get the tenant
domain .. Is there any reason why
Hi All,
This is to brief and discuss about the architecture of the $subject. So
here's how it works.
We gonna enable both GCM and Local push as switchable options so that
depending on the requirement, we can choose which method to go with.
Android's native service such as AlarmManager will be
+1 for using a regex which is more readable and maintaiwnance friendly.
Touched, not typed. Erroneous words are a feature, not a typo.
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Nice !!
Three things:
1. We need to work on graph titles. While going through the graphs I
realized these can be better worded.
2. Let's also try to extend these to drill downs where ever possible.
eg:
Now we show number of API calls/Application (%).
We can extend this such that, when clicked
Dinusha,
Let's schedule a discussion today with Azeez, Shankar Prabath.
On Thu, Apr 10, 2014 at 6:18 AM, Dinusha Senanayaka dinu...@wso2.comwrote:
Hi,
We have identified following ares to be cover with $subject. Additionally
we need to define features that could be useful for users, like
Hi GayanK,
In building input and output trees at what point we decide the tree
building has been completed and schemas needs to be generated based on the
constructed trees?
Thanks and Regards,
AsankaS.
On Wed, Apr 9, 2014 at 6:08 PM, Susinda Perera susi...@wso2.com wrote:
Hi Harshana
Yes
Hi,
On Thu, Apr 10, 2014 at 8:45 AM, Asanka Sanjeewa asan...@wso2.com wrote:
Hi GayanK,
In building input and output trees at what point we decide the tree
building has been completed and schemas needs to be generated based on the
constructed trees?
Ideally schema should generate when
Hi Kasun,
We gonna enable both GCM and Local push as switchable options so that
depending on the requirement, we can choose which method to go with
Just to clarify does this use both local and push notifications at once or
we allow to switch one based on the implementation?
Regards,
Dilshan
Hi Kasun,
I think we must implement the method you are proposing. Since this
AlarmManager system service will wakeup our EMM agent in every 10 mins (or
in configured intervals) it will make sure that our EMM agent is running in
the device. Otherwise there would be no way that we could guarantee
+1 for local notifications. There are some tasks which need to happen real
time and some tasks which does need to happen on time. If we can
distinguish them properly we can save large amount of battery power.
On Thu, Apr 10, 2014 at 10:34 AM, Harshan Liyanage hars...@wso2.com wrote:
Hi Kasun,
@Dilshan - We can actually allow switching. But there might be a scenario
where we might need both. That's totally depends on the scenario where it
will be used.
On Thu, Apr 10, 2014 at 10:41 AM, Chathura Dilan chathu...@wso2.com wrote:
+1 for local notifications. There are some tasks which
Hi all,
Please find comments inline.
On Thu, Apr 10, 2014 at 9:35 AM, Lali Devamanthri l...@wso2.com wrote:
Hi,
On Thu, Apr 10, 2014 at 8:45 AM, Asanka Sanjeewa asan...@wso2.com wrote:
Hi GayanK,
In building input and output trees at what point we decide the tree
building has been
I believe its better to use them both since in some scenarios if we have
dynamic policies (time based etc. ) which is created from EMM this will be
needed. Hence we need to think about a way to have them work when
necessary.
On Thu, Apr 10, 2014 at 10:45 AM, Kasun Dananjaya Delgolla
19 matches
Mail list logo
