Hi Prabath,
On Mon, Oct 24, 2016 at 6:31 AM, Prabath Siriwardana
wrote:
> Hi Ishara,
>
> +1 for the proposal... let's create a RM so we will not miss this... also
> let's do a brainstorming session on this...
>
Sure will create a RM and schedule a brainstorming session.
Hi all,
Amazon S3 provides a simple web services interface that can be used to
store and retrieve any amount of data, at any time, from anywhere on the
web.There is already amazon S3 connector in store. Now I am doing
improvement Creating the URL signing for S3 connector [1]. Here I focused
to
Hi Vivekananthan,
Please check if it make sense to remove those? I am just suggesting :)
On Mon, Oct 24, 2016 at 4:55 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:
> Noted Malaka.
>
> Vivekananthan Sivanayagam
> Associate Software Engineer | WSO2
> E:vivekanant...@wso2.com
>
Noted Malaka.
Vivekananthan Sivanayagam
Associate Software Engineer | WSO2
E:vivekanant...@wso2.com
M:+94752786138
On Mon, Oct 24, 2016 at 4:42 PM, Malaka Silva wrote:
> Hi Vivekanathan,
>
> I guess we can skip Folders and Templates
> for the initial version?
>
> I think
Hi Vivekanathan,
I guess we can skip Folders and Templates
for the initial version?
I think those won't be used in most of the use cases?
On Mon, Oct 24, 2016 at 3:37 PM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:
> Hi All,
>
> MailChimp is an online email marketing solution
Hi All,
MailChimp is an online email marketing solution to manage subscribers, send
emails, and track results. An existing connector was developed to support
2.0 [1] and MailChimp API v3.0 [2]is now live. The current version (2.0)
will no longer be supported after 2016.
I am going to implement
The flat file approach is also an option for us, thanks for suggesting it
Akila. At the moment we dont have a feature to make use of audit
information and it is not a priority for us to implement. So we will
revisit our options latter on if we do decide to implement this.
On 23 October 2016 at
Hi All,
Current Dropbox connector is implemented based on Dropbox API V1 which is
deprecated now. So I am planning to rewrite the connector for API V2 with
the following methods:
*Files and Metadata:*
- getFile: Downloads a file.
- uploadFile: Uploads a file.
- getMetadata: Retrieves
I also think the better approach would be to ship only the connectors with
the 'Stream Processor' distribution and let the binaries be separate
downloads.
Since Spark, etc are optional for the key area we are focusing on 'stream
processing', having them in the distribution it self might not be
So it is like we have a well defined Agent which defines the OIDC flow. We
can call the methods of the Agent when we write the Valve or the Filter. We
do not need to know about the library used in the agent to complete the
task.
Here we are initially implementing the valve.
Another benefit is as
I completed the HdrHIstogram integration with Carbon Metrics. Please check
the commits in my personal repository for now [1]. I'll send a PR later.
Thanks!
[1] https://github.com/chrishantha/carbon-metrics/commits/master
On Mon, Oct 17, 2016 at 11:30 AM, Malith Jayasinghe
11 matches
Mail list logo