[wsf-c-dev] Re: [] XMPP server side transport

[Damitha Kumarage]

Damitha Kumarage wrote:

>
>> What if think about this like this. A transport is an abstract entity 
>> which is been used by the server and the client both to send messages 
>> to each other.
>>
>> With that, HTTPTranport is a Transport, TCPTransport is a Transport, 
>> XMPPTransport is a Transport.
>>
>> So now the problem is pushed down to a level where we only need to 
>> worry about delivering a message from A to B. HTTP can do that, TCP 
>> can do that, XMPP can do that too.
>>
>> When I want to chat with some one I have mention the jabber ID of 
>> that individual so that jabber can find the end point to deliver the 
>> message, like in HTTP we have to tell an URL or in TCP IP:PORT.
>>
>> So then the question is how much do we have of such a XMPP transport 
>> at this point?
>>
>> Does this make sense with the current Axis-C design?
>>
>>  
>>
> What Ishan has implemented is a xmpp client transport which enable us 
> to expose a axis2 serivce
> as following
>
>    chat_client ---------------------->jabber 
> server------------------------->axis2_service
>                      <---------------------                       
> <-----------------------
> In testing scenario we type a soap message in the chat window which is 
> wrppaed in the xmpp message body and sent to the jabber server. 
> axis2_service will receive this(as a chat client) and
> using xmpp client transport(implemented using iksemel as parser) 
> extract the soap message and pass to the axis2c engine. Then the 
> response from the service is again wrapped inside the xmpp message and 
> sent back to the chat client.
> AFAIK this is what ishan has implemented as xmpp client transport. I 
> think to enabling the required scenario what we need to do is
> axis2c_client ---------------------->jabber 
> server------------------------->axis2_service
>                     <---------------------                       
> <-----------------------
>
> I think this involve relatively easy work since ishan has implemented 
> and tested the first scenario.


To be more precise what we need to do is to figure out how the service 
client api can be used for xmpp and provide the neccessary changes to 
the client xmpp transport to achieve this if any.
Also note that in the second scenario above both axis2c_client and 
axis2c_service are jabber clients. So to be clear we are not 
implementing any server transport for xmpp.
Damitha