[jira] Commented: (AXIS2C-1178) Implement AMQP Transport

2008-06-05 Thread Danushka Menikkumbura (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2C-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602903#action_12602903 ] Danushka Menikkumbura commented on AXIS2C-1178: --- Thiago, The AMQP transpor

[jira] Created: (AXIS2C-1180) SSL Communication and the CA certificate

2008-06-05 Thread Frank Huebbers (JIRA)
SSL Communication and the CA certificate Key: AXIS2C-1180 URL: https://issues.apache.org/jira/browse/AXIS2C-1180 Project: Axis2-C Issue Type: Bug Components: transport/http Affects Versi

[jira] Commented: (AXIS2C-1178) Implement AMQP Transport

2008-06-05 Thread Thiago Rafael Becker (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2C-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602793#action_12602793 ] Thiago Rafael Becker commented on AXIS2C-1178: -- Why are you using C++ instead

Re: Moving axis2_*iis/apache2*_worker_process_request logic to a common place - Correct mail

2008-06-05 Thread Nandika Jayawardana
+1. I think this is a good approach. I think we should have the message context as a member variable in both of these variables. In that way, what ever the module specific information can be passed through message context. Since this is specific to http, I think these two structures should rather

Re: Next release?

2008-06-05 Thread Dinesh Premalal
Hi Manjula, Manjula Peiris <[EMAIL PROTECTED]> writes: >> Are we going to include MTOM caching in this release ? > > Receiving side is ok .I am working at sending side. Seems to me we need > to fix http chunking at our client transport. What I really mean is , we need to decide whether to include

Re: Next release?

2008-06-05 Thread Manjula Peiris
On Thu, 2008-06-05 at 15:13 +0530, Dinesh Premalal wrote: > Hi, > > Samisa Abeysinghe <[EMAIL PROTECTED]> writes: > > > Time to discuss next release? > > Are we going to include MTOM caching in this release ? Receiving side is ok .I am working at sending side. Seems to me we need to fix http c

Re: Next release?

2008-06-05 Thread Dinesh Premalal
Hi, Samisa Abeysinghe <[EMAIL PROTECTED]> writes: > Time to discuss next release? Are we going to include MTOM caching in this release ? thanks, Dinesh -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For addi

Re: Next release?

2008-06-05 Thread Supun Kamburugamuva
Hi, IIS 6 and 7 support will be good features to the next release. It will take another one or two weeks. Supun.. On Thu, Jun 5, 2008 at 1:05 AM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: > Time to discuss next release? > > Samisa... > > >

Moving axis2_*iis/apache2*_worker_process_request logic to a common place - Correct mail

2008-06-05 Thread Supun Kamburugamuva
Hi List, We have a very large code inside both axis2_apache2_worker_process_request and axis2_iis_worker_process_request methods. Both these codes are similar and use the same logic. It is hard to maintain the same code in may places and I would like to suggest to move the common logic in to the h

Next release?

2008-06-05 Thread Samisa Abeysinghe
Time to discuss next release? Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Moving axis2_*iis/apache2*_worker_process_request logic to a common place

2008-06-05 Thread Supun Kamburugamuva
Sorry, Please ignore this mail. Before I finish the mail my mail client sent it. I must have accidentally hit return -). On Thu, Jun 5, 2008 at 12:56 AM, Supun Kamburugamuva <[EMAIL PROTECTED]> wrote: > Hi List, > > We have a very large code inside both axis2_apache2_worker_process_request > and

Moving axis2_*iis/apache2*_worker_process_request logic to a common place

2008-06-05 Thread Supun Kamburugamuva
Hi List, We have a very large code inside both axis2_apache2_worker_process_request and axis2_iis_worker_process_request methods. Both these codes are similar and use the same logic. It is hard to maintain same code in two places and I would like to suggest to move the common logic in to the http_