Hi,
As Johann mentioned, if the specification defined sending token as the
query param, we needs to support it and implement as specification
specified. But again the user who going to use it needs to know aware of
the security issues cause by using token as query param. Also the
specification spe
Hi,
Given you use HTTP, If the request is intercepted, keys are exposed even
you send as URL or as headers.
If you use https, headers and URL are both encrypted I guess. However
sending in URL has some drawbacks,
1) browsers caches the URL
2) will be printed in logs ad Johans mentioned
So bette
Would that needs tools.jar in the classpath?
One advantage of scala are lamba function (e.g. see Sameera's slides on
java 8) .. but disadvantage is you need to learn scala a bit.
--Srinath
On Fri, Nov 21, 2014 at 4:43 PM, Rajeev Sampath wrote:
>
> On Fri, Nov 21, 2014 at 10:40 AM, Srinath Pere
IMO, use of window batch is consistant (My argument is, it is interpreted
as batch process when used with event tables). But lets think more on that.
--Srinath
On Sat, Nov 22, 2014 at 7:56 AM, Sriskandarajah Suhothayan
wrote:
> +1
> I like the idea, only worried about the use of *#window.batch(
+1
I like the idea, only worried about the use of *#window.batch()*
How about using *WeatherStream#pull#window.time(24h) *instead?
Suho
On Fri, Nov 21, 2014 at 8:33 PM, Srinath Perera wrote:
> Hi All,
>
>
> I think I have finally figured out a way do the Paul's idea (See the
> thread "Unifying
Hi All,
I think I have finally figured out a way do the Paul's idea (See the thread
"Unifying CEP and BAM Languages"
http://mail.wso2.org/mailarchive/architecture/2014-May/016366.html for more
details).
Currently event tables in Siddhi are backed by a disk and can be used to
joins
However, you
Hi All,
The method that Udara mentioned would indeed improve performance. but when
we scale it up to couple hundred or more applications again this will
become a overhead. So how about introducing a map ( as an cache ) that
keeps all the invocation data until the map is written to the database
per
First of all this is highly discouraged way of sending the access token,
mainly because you will find it in the http access logs.
Still if you want to go ahead an implement it, it must follow the
specification at [1].
However we should discourage using this approach.
[1] https://tools.ietf.org/htm
Hi all
I’m developing $Subject for APIM
Currently the access token is passed in the Authorization header and now
i’m planning to Implement this feature by sending access token in the
query string using the parameter name "authkey" as shown below,
Eg :-
http://10.100.5.192:8280/twitter/1.0.0?q=w
Great!
On Fri, Nov 21, 2014 at 3:20 PM, Afkham Azeez wrote:
> I tested AWS clustering in the last couple of days, and it is working
> without any code changes. Just need to provide the AWS connection
> parameters etc. in the clustering section. However, it won't work with ELB
> because we have t
I tested AWS clustering in the last couple of days, and it is working
without any code changes. Just need to provide the AWS connection
parameters etc. in the clustering section. However, it won't work with ELB
because we have to change the ELB component to read the proper AWS security
group name f
On Fri, Nov 21, 2014 at 10:40 AM, Srinath Perera wrote:
> Useful to have in competition with Storm. Performance is the concern.
>
> One ida is to get extensions as scala function and running is using
> https://code.google.com/p/scalascriptengine/
>
>
This will be a very useful feature to have.
A
Hi Lasantha
IMO API comments and subscriptions should not be in the import/export it
should be only limited to API definition , Management info and the
documents. If you are exporting subscriptions it will require you to have
the exact apps and users in the imported destination as well which will
Hi Jo,
In that case, we will be using the swagger docs stored in registry to get
the swagger definition when exporting and use the existing API to
add/update when importing. I think there is a certain subset of
metadata/information (captured after deploying the API) that is not
captured by the swa
14 matches
Mail list logo
