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 "Sahan Gamage (JIRA)" <ji...@apache.org> on 2006/01/25 04:02:58 UTC

[jira] Commented: (AXIS2C-8) Clearly seperate abstraction layer from core transport to accomodate alternative transport implementations

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

Sahan Gamage commented on AXIS2C-8:
-----------------------------------

There should be an abstraction of the transport for axis2 for different implementations (e.g: HTTP, SMTP). Also inside these implementations there should be abstractions to plugin different libraries for various tasks (e.g: using libcurl for the HTTP client side functionality). These abstractions can be defined in header files and the different implementations can include these headers and implement accordingly.

> Clearly seperate abstraction layer from core transport to accomodate alternative transport implementations
> ----------------------------------------------------------------------------------------------------------
>
>          Key: AXIS2C-8
>          URL: http://issues.apache.org/jira/browse/AXIS2C-8
>      Project: Axis2-C
>         Type: Improvement
>   Components: transport/http
>     Reporter: Samisa Abeysinghe
>     Assignee: Sahan Gamage

>
> At the moment the transport implemenation is mixed up the implementation with abstraction layer. Ideally we should seperate the abstraction layer to help others interested in implementaing laternative transports

-- 
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