Errors written to the log file in param_container.c file
-
Key: AXIS2C-1064
URL: https://issues.apache.org/jira/browse/AXIS2C-1064
Project: Axis2-C
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/AXIS2C-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Pushpakumara updated AXIS2C-1064:
---
Attachment: param_container.diff
> Errors written to the log file in param_container
On Tue, 2008-03-18 at 03:49 +0530, Samisa Abeysinghe wrote:
> Thilina Gunarathne wrote:
> >> However, the real issue is how are we going to implement "parse it for
> >> MIME, and then cache it and move on". I still think that it is better to
> >> stick to Thilina's viewpoint in having each atta
Hi Samisa, Senaka and Thilina,
These are my view points on caching and how it can be done in Axis2/C.
For me the main purpose of caching is to support any size of attachment
which depends only on the folder size the attachment is going to be
stored.
In the current implementation (Axis2/C 1.3) we
[
https://issues.apache.org/jira/browse/AXIS2C-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senaka Fernando resolved AXIS2C-1061.
-
Resolution: Fixed
Fixed Issue
> Ability for Simple Axis2 HTTP Server to specify Date an
Hi Manoj,
When creating a JIRA please try to be specific about the JIRA
summary, In this case you could have been more specific about the
change.
thanks,
Dinesh
"Manoj Pushpakumara (JIRA)" <[EMAIL PROTECTED]> writes:
> [
> https://issues.apache.org/jira/browse/AXIS2C-1062?page=c
> Well, the Java folks have the luxury of streams. C has to manage this at
> socket level. So my question was, how are we supposed to do that with C
> network handler?
I'm not familiar with the workings of the C network handler. But for us the
only useful part of the input stream was the read() me
Thilina Gunarathne wrote:
>> Also you might want to consider deferred parsing of attachments. That
>> means read the attachment for the stream only when needed.
This is what the Java does.
That's why I proposed you people to consider doing it in C :)..
In Axis2/Java we first parse o
>> Also you might want to consider deferred parsing of attachments. That
> >> means read the attachment for the stream only when needed.
>
> This is what the Java does.
That's why I proposed you people to consider doing it in C :)..
In Axis2/Java we first parse only the SOAP part (MIME part con
Also you might want to consider deferred parsing of attachments. That
means read the attachment for the stream only when needed.
This is what the Java does. How can you do this in C?
Samisa...
-
To unsubscribe, e-mail: [EM
Senaka Fernando wrote:
Ideally it should be either the Content-Length or if Chunked then we'll
have to read until the end of chunks. So, if you see Content-Length,
then
no need to calculate size while parsing. You already know it. But, your
proposal is valid for the Chunked case.
I'm
Thilina Gunarathne wrote:
However, the real issue is how are we going to implement "parse it for
MIME, and then cache it and move on". I still think that it is better to
stick to Thilina's viewpoint in having each attachment cached as a
separate file. And, each attachment should be cached, ev
Senaka Fernando wrote:
Manjula Peiris wrote:
On Sun, 2008-03-16 at 16:26 +0530, Samisa Abeysinghe wrote:
We have an efficient parsing mechanism already, tested and proven to
work, with 1.3. Why on earth are we discussing this over and over
again?
Does caching get affected by the
[
https://issues.apache.org/jira/browse/AXIS2C-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senaka Fernando resolved AXIS2C-1063.
-
Resolution: Fixed
Fix Version/s: Current (Nightly)
Assignee: Senaka Ferna
modified the md5.c file
-
Key: AXIS2C-1063
URL: https://issues.apache.org/jira/browse/AXIS2C-1063
Project: Axis2-C
Issue Type: Improvement
Reporter: Manoj Pushpakumara
Priority: Minor
[
https://issues.apache.org/jira/browse/AXIS2C-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Pushpakumara updated AXIS2C-1063:
---
Attachment: md5.diff
> modified the md5.c file
> -
>
>
[
https://issues.apache.org/jira/browse/AXIS2C-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjaya Ratnaweera resolved AXIS2C-1062.
Resolution: Fixed
Fix Version/s: Current (Nightly)
Patch applied. Thanks Ma
[
https://issues.apache.org/jira/browse/AXIS2C-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjaya Ratnaweera reassigned AXIS2C-1062:
--
Assignee: Sanjaya Ratnaweera
> modified the network_handler.c file
> -
[
https://issues.apache.org/jira/browse/AXIS2C-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Pushpakumara updated AXIS2C-1062:
---
Attachment: network_handler.diff
> modified the network_handler.c file
> ---
modified the network_handler.c file
---
Key: AXIS2C-1062
URL: https://issues.apache.org/jira/browse/AXIS2C-1062
Project: Axis2-C
Issue Type: Improvement
Reporter: Manoj Pushpakumara
Pri
Hi All,
Currently I am working on the Axis2c 1.2 to make it communicate with a legacy
system. I have gone through the architecture given in the manual on the
website. But from that I am not able to get the exact idea of the flow of the
request.
Kindly let me know the architecture of the Axis2
21 matches
Mail list logo
