axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Commented: (AXISCPP-659) Move connection opening out of flushOutput method
Date Wed, 25 May 2005 11:15:51 GMT
     [ ]
Samisa Abeysinghe commented on AXISCPP-659:

I think the best place where we could call Transport::openConnection is in ClientAxisEngine::invoke()
method. I tried including it like the following inside invoke:

        if (AXIS_SUCCESS != (Status = m_pSZ->setOutputStream (m_pSoap)))


So before calling markEndOfStream whuch calls Transport::flushOutput(), I open the connection.
flushOutput will only other about writing to the stream, and not open the connection.

> Move connection opening out of flushOutput method
> -------------------------------------------------
>          Key: AXISCPP-659
>          URL:
>      Project: Axis-C++
>         Type: Improvement
>   Components: Transport (axis3)
>     Versions: 1.5 Final
>     Reporter: Samisa Abeysinghe
>     Assignee: Samisa Abeysinghe
>      Fix For: 1.6 Alpha

> Connection opening should not be the responsibility of the flushOutput method. Rather
it has to be an independent act.
> When connection opening is within the flushOutput, it becomes harder to debug. Hence
it is ideal to move this to out of flushOutput.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message