[
https://issues.apache.org/jira/browse/SYNAPSE-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udayanga Wickramasinghe updated SYNAPSE-749:
Attachment: synapse_SYNAPSE-749_cache.patch
> Implementing separate Ca
Implementing separate Cache for Synapse
---
Key: SYNAPSE-749
URL: https://issues.apache.org/jira/browse/SYNAPSE-749
Project: Synapse
Issue Type: New Feature
Components: Core
Reporter
Hi Hiranya,
Actually our original intention was to introduce pre-fetching for the
registry entries. But then we realized that the caching in mixed with
the registry of the synapse. Ideally registry is the content provider.
But we use the registry for caching as well. This makes the
synchronization
Hi Supun
On Mon, Jan 10, 2011 at 12:01 PM, Supun Kamburugamuva wrote:
> I think cache is not something a user should think in terms of
> mediation. So I'm thinking that it should go in to a separate file.
> Only the people who write code will see the cache.
>
So this is a plus point for the curr
On Mon, Jan 10, 2011 at 10:11 AM, Udayanga Wickramasinghe wrote:
> Hi devs,
> i think it is better we do $subject for Synapse . There is already a cache
> implementation for synapse which store and manage endpoints, remote entries
> ,etc. However the problem is all cache related functions are cur
Hi,
On Mon, Jan 10, 2011 at 12:20 PM, indika kumara wrote:
> Udayanga, if you are going to implement a cache, please have a look at the
> 'Caching Application Block'[1]'. Furthermore, have a look at the .Net cache
> architecture (or any other research). Also you may use wso2's cache
> implementat
Folks,
We (Supun, Indika, Udayanga and myself) had an off-line chat on this and we
have decided to start with refactoring the existing caching capability and
trying to improve it.
Ruwan
On Mon, Jan 10, 2011 at 12:20 PM, indika kumara wrote:
> Udayanga, if you are going to implement a cache, ple
Udayanga, if you are going to implement a cache, please have a look at the
'Caching Application Block'[1]'. Furthermore, have a look at the .Net cache
architecture (or any other research). Also you may use wso2's cache
implementation with or without modifications. Re-usability is key as the
cache i
I think cache is not something a user should think in terms of
mediation. So I'm thinking that it should go in to a separate file.
Only the people who write code will see the cache.
This lead us to think about the Registry definition in the synapse.xml
as well. The registry definition that is in t
Also you have neglected my question on the relation to the configuration
language with this, or are you planning to make this completely transparent
from the user?
Ruwan
On Mon, Jan 10, 2011 at 11:52 AM, Ruwan Linton wrote:
>
>
> On Mon, Jan 10, 2011 at 11:35 AM, Udayanga Wickramasinghe <
> uday
On Mon, Jan 10, 2011 at 11:35 AM, Udayanga Wickramasinghe wrote:
> Hi Ruwan,
>
> On Mon, Jan 10, 2011 at 10:32 AM, Ruwan Linton wrote:
>
>> Udayanga, may I know some usecases for this cache implementation?? Synapse
>> is not designed for the users to interact with the API directly. It has a
>> co
Hi Ruwan,
On Mon, Jan 10, 2011 at 10:32 AM, Ruwan Linton wrote:
> Udayanga, may I know some usecases for this cache implementation?? Synapse
> is not designed for the users to interact with the API directly. It has a
> configuration language to access the API (in most of the cases, apart from
> t
Udayanga, may I know some usecases for this cache implementation?? Synapse
is not designed for the users to interact with the API directly. It has a
configuration language to access the API (in most of the cases, apart from
the Class mediator and so forth, and the class mediator has to be your last
Hi devs,
i think it is better we do $subject for Synapse . There is already a cache
implementation for synapse which store and manage endpoints, remote entries
,etc. However the problem is all cache related functions are currently done
in Synapse configuration and Registry,etc modules, which is no
14 matches
Mail list logo
