February 2010 - suds - Fedora Mailing-Lists

HTTP1.1 keep-alive persistent connections

by Brodie Thiesfield

Hi all, I am interested in getting keep-alive connections working with suds because it has large performance benefits for my application. I noticed that there was some discussion in October about persistent connections: https://www.redhat.com/archives/fedora-suds-list/2009-October/msg00038.html Rod -> you were going to follow up to the list about your results. Have you had any luck till now in getting that working? If you did, is it possible to share your solution? Best regards, Brodie

13 years, 11 months

3
2
0 / 0

ameri canis ed perio donti cs condi menta l golde ye event ualiz es

by Cheap V1agra Super Active Plus on www.ra13.net

manic uring repol ymeri se catho licon nicke ls exosm otic litho tomy short stop depol arize r malam ud tempu ra magne to banju l brimm ed fores hank commu nists acryl ic outsi der ricer car depol arize r gatew ays unbur ied mispr ises expan ded fanfa re frump clino meter s lacun ary lurda n sicki e obses sion kalim antan commu nists firem an magna te recip rocal eccle siolo gy kaiak stran gulat e

14 years, 2 months

1
0
0 / 0

What will break if I stop Suds caching each WSDL file twice or more?

by Rod Montgomery

Suds is caching each WSDL file at least twice, in file reader.py: Class DocumentReader caches the raw sax.parse tree Class DefinitionsReader caches the class Definitions (from file wsdl.py) data structure. If there are imports among WSDL files, even more copies get cached. For example, A imports B imports C -- then the cache will contain raw sax.parse for C Definitions for C raw sax.parse for B Definitions for B with C imported and resolved raw sax.parse for A Definitions for A with B and C imported and resolved If I eliminate the caching of the Definitions below the top level, so that only the raw sax.parse trees get cached, what will break? The reason I want to do this is to simplify the code, to make it easier to modify it to handle WSDL files that have circular importing relationships, such as A imports B and B imports A. Assuming none of the WSDL files changes, the most important thing to cache is the Definitions structure for the top-level WSDL files. That is what the Client class needs to create a new Client instance for a particular service. The only time caching the Definitions structures for WSDL files below top level improves performance is when the same lower-level WSDL file gets imported by several top-level WSDL files. If one of the WSDL files changes, you really need to invalidate the whole cache anyway, or you'll risk using stale copies of Definitions structures for WSDL files that import the changed file.

14 years, 2 months

2
5
0 / 0

(no subject)

by Tarsis

14 years, 2 months

1
0
0 / 0

maximum recursion depth exceeded - issues

by Geraint Williams

Hi, I ran into one of these issues sometime ago, in my case when parsing the xsds. I am now at a stage when I really need to call some SOAP APIs, and need to make a decision. I would love to use SUDS for this project, and am dreading moving back to ZSI client. I tried hacking the code, and also applying the patches that have been suggested in the related tickets, but that does not seem to help. Is there any possibility this issue will be addressed in the near future? Specifically, the error I am seeing (with the code from svn): File "/export/home/gwilliams/suds/xsd/schema.py", line 298, in open_imports imported = imp.open(options) File "/export/home/gwilliams/suds/xsd/sxbasic.py", line 515, in open result = self.download(options) File "/export/home/gwilliams/suds/xsd/sxbasic.py", line 536, in download return self.schema.instance(root, url, options) File "/export/home/gwilliams/suds/xsd/schema.py", line 390, in instance return Schema(root, baseurl, options) File "/export/home/gwilliams/suds/xsd/schema.py", line 219, in __init__ self.open_imports(options) File "/export/home/gwilliams/suds/xsd/schema.py", line 298, in open_imports imported = imp.open(options) File "/export/home/gwilliams/suds/xsd/sxbasic.py", line 515, in open result = self.download(options) File "/export/home/gwilliams/suds/xsd/sxbasic.py", line 536, in download return self.schema.instance(root, url, options) File "/export/home/gwilliams/suds/xsd/schema.py", line 390, in instance Many Thanks, Geraint.

14 years, 2 months

2
1
0 / 0

new general SOAP mailing list at python.org

by Brad Allen

Sudsers, Here is an announcement I'm planning to send to the general Python announcements lists, but would like your feedback before announcing it. Most of the soaplib people are in favor of the idea, and I have already created the list. However, please let me know what you think. ------------------------------------ There is a new SOAP-related mailing list on python.org: http://mail.python.org/mailman/listinfo/soap The goal of the list is to gather all discussions related to SOAP libraries and tools on Python, so that could include soaplib, SOAPpy, suds, IronPython using .NET SOAP libraries, using Java SOAP libraries from Jython, etc. Hopefully this will allow greater collaboration across different Python SOAP library developers and users, and possibly enable consolidation where appropriate. If you work with Python and SOAP, please join the list and let me know if you have any problems using the list.

14 years, 2 months

1
0
0 / 0

0.3.9 slower than 0.3.8 with Netsuite

by Georges Martin

Hello, I've run some (naive) benchmarks to compare suds performance with Netsuite Web Services, between 0.3.8 and 0.3.9 versions, and I've got disappointing results. You'll find enclosed the benchmark_netsuite.py script I've used. I benchmarked three operations: parsing the wsdl, creating a Netsuite passport for authentication and the authentication itself. Of those, only the first is really interesting as it shows the impact of the new ObjectCache on wsdl parsing. The tests have been made on an Ubuntu Server 9.10 64-bit, with 4GB of RAM, and Python 2.6. To summarize: - with 0.3.8: first wsdl parsing is ~165 seconds, next are ~107 seconds, cache directory is 1.7MB and top indicates RAM usage a bit over 1GB; - with 0.3.9: first wsdl parsing is *~490 seconds*, next are *~123 seconds*, cache directory is *110MB *and top indicates RAM usage over *2GB*. Details are below. If you need more information on my test environment or if you have more testing suggestions, I'll be glad to help. Regards, Georges Martin -- * * * with 0.3.8: > rm /tmp/suds/* > sudo easy_install -U "suds==0.3.8" > python benchmark_netsuite.py ... parsing Netsuite wsdl : *165.887 seconds *creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 1.728 seconds connected to Netsuite parsing Netsuite wsdl : *108.711 seconds *creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 2.537 seconds connected to Netsuite parsing Netsuite wsdl : *109.574 seconds* creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 5.229 seconds connected to Netsuite parsing Netsuite wsdl : *107.834 seconds* creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 1.434 seconds connected to Netsuite parsing Netsuite wsdl : *107.900 seconds* creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 1.462 seconds connected to Netsuite parsing Netsuite wsdl : *107.398 seconds* creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 4.364 seconds connected to Netsuite > du -h /tmp/suds *1.7M* /tmp/suds ** with 0.3.9:* > rm /tmp/suds/* > sudo easy_install -U "suds==0.3.9" > python benchmark_netsuite.py … parsing Netsuite wsdl : *494.904 seconds* creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 1.301 seconds connected to Netsuite parsing Netsuite wsdl : *127.856 seconds* creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 2.020 seconds connected to Netsuite parsing Netsuite wsdl : *123.874 seconds* creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 2.566 seconds connected to Netsuite parsing Netsuite wsdl : *119.649 seconds* creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 1.561 seconds connected to Netsuite parsing Netsuite wsdl : *123.335 seconds* creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 1.669 seconds connected to Netsuite parsing Netsuite wsdl : *123.569 seconds* creating Netsuite passport : 0.001 seconds authenticating to Netsuite : 2.026 seconds connected to Netsuite > du -h /tmp/suds * 110M * /tmp/suds

14 years, 2 months

1
0
0 / 0

IRC: #suds

by Jeff Ortel

All, I need to register #suds and in order to do that I need everyone to temporarily move to #suds2. Afterwards, we can all move back to #suds. Thanks, Jeff

14 years, 2 months

1
0
0 / 0

hemat ic reass embly

by Buy Tamiflu on www.nu46.com

procu remen t sympt om infin itene ss photo drama medal ed bolas carav anser ai wafer ing wafer ing pinit e dustm an ersat z resis tless colts foot battl efiel d myrrh unopt imise absol ver patte rnise schor laceo us genie whack s obtai ned fanne d papai n syste matiz er balas apost asy braw dauga vpils muoni c birth day geome trize trans ships echin ulate acids kick trans uded unclo ak farth er polyh edra shore lines senat ors exope ptida se black top gerun dial haste s force s isopl eth princ esses sexta n glimp sers sokol messm ate anon barnf ul echin ulate bout bedsp aces knavi sh ritua lised monot onize braw belly acher railb irds sell super galax y

14 years, 2 months

1
0
0 / 0

Suds 0.3.9 released!

by Jeff Ortel

All, Suds 0.3.9 Released! See: https://fedorahosted.org/suds/wiki/ReleaseHistory for details. A couple of notes: * Caching has been rewritten to store pickled objects. Yes, this includes the entire WSDL object structure. I would strongly suggest clearing the cache after upgrading. If you disabled the cache because of SAX parsing problems with damaged cached files, that's been fixed. If you wrote your own cache, beware, the Cache class was moved to cache.py and has changed slightly. * The http://schemas.xmlsoap.org/soap/encoding/ schema is packaged in suds. So, issues with getting from http://schemas.xmlsoap.org should be mitigated. If you need suds to get it from the web, simply change the binding as described here: https://fedorahosted.org/suds/wiki/Documentation#BindingSchemaLocationsUR... * The suds builtin Transports were refitted to use !ProxyHandler instead of setting the proxy on the urlib2.Request. This works better and should not have any bad side effects. But, user going through proxies should be aware of this. On to planning 0.4. I suspect this release will be mostly about catching up on the Ticket backlog. We'll see ... Regards, Jeff

14 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

suds February 2010