The pyramid registry is effectively a singleton. There is only one per
Pyramid app. Thus, from your example code, you're creating 10 persistent
soap connections per instance of the app. If you're forking the server or
anything then this may explode the way you're describing. You need to come
up
We have tried other SOAP libraries in the past pysimplesoap for some reason
is the only one that works.
On Fri, Nov 16, 2018 at 4:58 AM Jens W. Klein wrote:
> On 14.11.18 17:42,
> bher...@uniqueinsuranceco.com wrote:
> > We are using pyramid for our insured portal at Unique Insurance.
> > We
On 14.11.18 17:42,
bher...@uniqueinsuranceco.com wrote:
> We are using pyramid for our insured portal at Unique Insurance.
> We have had great success with pyramid and still use it to this day!
> However we have hit a problem, when we use the pyramid.registry and
> register an SOAP object to the
On Thursday, November 15, 2018 at 5:43:56 PM UTC-5, Brian Herman wrote:
>
> Oh cool there is sorry for the spam
> https://docs.pylonsproject.org/projects/pyramid-cookbook/en/latest/deployment/forked_threaded_servers.html
>
>
it depends on the container you run pyramid in - they each have a
Oh cool there is sorry for the spam
https://docs.pylonsproject.org/projects/pyramid-cookbook/en/latest/deployment/forked_threaded_servers.html
On Thu, Nov 15, 2018 at 4:30 PM Brian Herman
wrote:
> How do i defer the connection after the application forks? Is there like a
> application after
How do i defer the connection after the application forks? Is there like a
application after fork function in pyramid?
On Thu, Nov 15, 2018 at 4:24 PM Brian Herman
wrote:
> Thanks man I appreciate it!
>
> On Thu, Nov 15, 2018 at 4:19 PM Jonathan Vanasco
> wrote:
>
>> A few things that jump out
Thanks man I appreciate it!
On Thu, Nov 15, 2018 at 4:19 PM Jonathan Vanasco wrote:
> A few things that jump out at me:
>
> 1. it looks like your `PN` class is creating 10 different `Client` objects
> which each start a persistent(?) connection to the SOAP server when
> created. that's a huge
A few things that jump out at me:
1. it looks like your `PN` class is creating 10 different `Client` objects
which each start a persistent(?) connection to the SOAP server when
created. that's a huge factor in overloading the connections.
2. I'm not familiar with your SOAP library. are these
Is there anyway to force the pyramid registry to have one instance of
itself or only of one reference of a signal object?
On Wednesday, November 14, 2018 at 10:42:15 AM UTC-6,
bhe...@uniqueinsuranceco.com wrote:
>
> We are using pyramid for our insured portal at Unique Insurance.
> We have had
