Re: How to make SOAP messages smaller?
Philipp Leitner schrieb: Sorry, no actual experience ... but I guess integrating it with Axis or Axis2 should be rather easy to do. If you plan to do anything in this direction it would be nice to keep us on the run. I'd love to, but since my master thesis is almost done and since I declined the offer to become a PhD student, I won't be able to do it anymore. But I will recommend another thesis with this topic in the chapter Future Work. Thx for your help, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I have fixed the some bugs in axis2 and attaching updates
donald yang schrieb: 1. Hot update web services that load native library. When you develop web services as a wrapper of native library(e.g., .dll or .so library), you can NOT hot update the web service as JVM will tell you that the dll has been loaded. The simple solution is to force JVM run garbage collector. So I updated *DeploymentEngine.java *and what I have changed is to add System.gc() twice at end of the method *unDeploy()*(Line number 681 and 682). Hmm, you cannot *force* the JVM to run the garbage collector. Even if your solution might run for you I suspect that it does not guarantee this behavior. See for example http://www.jguru.com/faq/view.jsp?EID=13932 Cheers, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to make SOAP messages smaller?
Hi there, I am currently making a scientific application web service ready. Since the data that gets transferred can be quite big, I am looking for a good solution to make the SOAP messages small. The input data, which consist mainly of doubles is usually given in binary files. I can use WS-Attachments to transfer those files, but I also have an RPC version, which sends human readable messages with ASCII data. Sadly, the blow-up using RPC style is just incredible, so I am looking into possibilities to make the SOAP messages smaller and still retain clearer interface and easy debugging using RPC. What techniques can I use to compress the data? Is there a better approach then just send binary files? Is it possible to use RPC, but have the doubles sent as binary? TIA, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to make SOAP messages smaller?
Ryan Nelsestuen schrieb: It sort of depends on your architecture and who the callers are, but you can put a GZipFilter in front of your AxisServlet and compress it that way... of course, that means the client has to be capable of uncompressing gzip as well as indicating that they support gzip in an HTTP header... Thx for your input! I thought about HTTP compression before, but what I don't like, is that the SOAP message looks like garbage then to the human eye. Maybe I can find a solution to make it optional for the client. That would at least help the client developer to debug. -Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to make SOAP messages smaller?
Spies, Brennan schrieb:
This should be pretty easy to do...have the servlet filter check the
Accept-Encoding before applying GZIP compression. Then, when debugging,
have the client turn off this header.
Thanks, good hint!
Does anyone know better compression techniques than gzip? I found a
paper claiming much better compression than gzip:
@inproceedings{Werner:CompressingSOAP,
Author = {C. Werner and C. Buschmann and S. Fischer},
Booktitle = {Proceedings of the IEEE International Conference on Web
Services},
Month = {July},
Pages = {540-547},
Title = {Compressing SOAP Messages by using Differential Encoding},
Year = {2004}}
If my mind serves me right, I have also heard for years now, that people
are researching XML compression. Is there any advanced compression
algorithm available for Axis?
Cheers,
Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Aixs2]Monitoring SOAP message with TCPMon
Jiang Liu schrieb: But this is never success. what could I do? What does it mean, it never succeeds? Does the call time out? Just guessing, but have you taken a look to the console from which you started TCPMon? Are there exceptions printed? Cheers, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
