You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Nabeel Yoosuf (JIRA)" <ji...@apache.org> on 2006/05/04 03:08:17 UTC

[jira] Commented: (AXIS2C-154) Implement caching for dynamic invocation

    [ http://issues.apache.org/jira/browse/AXIS2C-154?page=comments#action_12377672 ] 

Nabeel Yoosuf commented on AXIS2C-154:
--------------------------------------

Apache httpd's moudles/cache may be a good pointer for this.

> Implement caching for dynamic invocation
> ----------------------------------------
>
>          Key: AXIS2C-154
>          URL: http://issues.apache.org/jira/browse/AXIS2C-154
>      Project: Axis2-C
>         Type: Task

>   Components: core/clientapi
>  Environment: All
>     Reporter: Nabeel Yoosuf

>
> To improve the performance, once the WSDL is parsed and the Object Model is create, we need to have caching facility at the client side. Subsequent requests can be served directly from the cache.
> I'd like to have something like this:
> /* user has the option of turning off caching*/
> #define AXIS2_WSDL_CACHE_NONE	0x0
> /* write the binary object model to file */
> #define	AXIS2_WSDL_CACHE_DISK 	0x1
> /* keep the object model in memory */
> #define	AXIS2_WSDL_CACHE_MEMORY	0x2
> typedef struct axis2_wsdl_cache_desc
> {
> 	int type;
> 	axis2_char_t *file_cache_dir;
> 	long ttl;
> 	long mem_upper_limit;
> } axis2_wsdl_cache_desc_t;
> * bitwise operations should allow to decide the type.
> 	e.g. AXIS2_WSDL_CACHE_DISK | AXIS2_WSDL_CACHE_MEMORY would cache in both memory and disk
> * when the disk cache is on, binary files are written to file_cache_dir folder
> * upon the expiration of ttl value, cached WSDL is removed
> * when in memory caching is used, mem_upper_limit would limit the maximum amount caching memory available. When the threshold is reached, older object models are removed first.
> * It's good to have an option to reset the cache if the user desires to do so.
> thanks
> -Nabeel

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira