I am using CXF 2.3.1, which I think supports Fast Infoset 1.2.8 and GZIP.
My first question has to do with the order of the interceptors. It's my impression that GZIP compression takes place after the results are marshalled into XML. Then, the whole HTTP response is GZIPed.
Would it be the same with Fast Infoset? There doesn't seem to be any issues with using both annotations on the SEI, I take it, as the client negotiates what they want?
The reason I'm asking is that some very large web service responses have, on occasion, run out of memory on the server during the encryption. CPU utilization seems to continue to grow. Adding GZIP would decrease my network latency at the expense of even more CPU processing time on the server, so perhaps it won't help much. It seems like to help with that problem, or to gain any performance benefits on the server, the Fast Infoset compression would have to take place before the ws-security encryption phase?
My other question is off-topic, I don't see any support in SoapUi for Fast Infoset (which seems strange), so I take it people measure the impact of this using custom written clients or other tools?
Regards,
Andrew
-----Original Message-----
From: Rafael Serina [mailto:rafael.serina [ at ] gmail.com]
Sent: Wednesday, March 12, 2014 5:54 AM
To: users [ at ] cxf.apache.org
Subject: remove from list
please remove me from this mailing list
Thanks
My first question has to do with the order of the interceptors. It's my impression that GZIP compression takes place after the results are marshalled into XML. Then, the whole HTTP response is GZIPed.
Would it be the same with Fast Infoset? There doesn't seem to be any issues with using both annotations on the SEI, I take it, as the client negotiates what they want?
The reason I'm asking is that some very large web service responses have, on occasion, run out of memory on the server during the encryption. CPU utilization seems to continue to grow. Adding GZIP would decrease my network latency at the expense of even more CPU processing time on the server, so perhaps it won't help much. It seems like to help with that problem, or to gain any performance benefits on the server, the Fast Infoset compression would have to take place before the ws-security encryption phase?
My other question is off-topic, I don't see any support in SoapUi for Fast Infoset (which seems strange), so I take it people measure the impact of this using custom written clients or other tools?
Regards,
Andrew
-----Original Message-----
From: Rafael Serina [mailto:rafael.serina [ at ] gmail.com]
Sent: Wednesday, March 12, 2014 5:54 AM
To: users [ at ] cxf.apache.org
Subject: remove from list
please remove me from this mailing list
Thanks