FW: [Pywebsvcs-talk] Another way to register objects?
Ivan R. Judson
judson at mcs.anl.gov
Mon Nov 3 11:09:48 CST 2003
> -----Original Message-----
> From: Warnes, Gregory R [mailto:gregory_r_warnes at groton.pfizer.com]
> Sent: Monday, November 03, 2003 10:53 AM
> To: 'judson at mcs.anl.gov'
> Cc: 'pywebsvcs-talk'
> Subject: RE: [Pywebsvcs-talk] Another way to register objects?
>
>
>
> The performance improvement was due a simple patch submitted
> by Erik Westra that dramatically improves parser performance
> by replacing
>
> string_variable = ''
> ...
> for ...:
> string_variable += more_string_data
>
> by
> list_of strings = []
> for ...:
> list_of_strings.append(more_string_data)
> string_variable = ''.join(list_of_strings)
>
> which avoids the repeated (invisible) string copying that is
> necessary to implement the append with Pythons immutible strings.
>
> Thanks to Erik for the work diagnosing and then fixing the problem.
>
> -G
>
> > -----Original Message-----
> > From: Ivan R. Judson [mailto:judson at mcs.anl.gov]
> > Sent: Friday, October 31, 2003 9:50 AM
> > To: judson at mcs.anl.gov; 'pywebsvcs'
> > Subject: RE: [Pywebsvcs-talk] Another way to register objects?
> >
> >
> >
> > Btw, what prompted this sudden migration (sudden to us), was
> > a small test
> > that showed that the SOAPBuilder.buildSOAP method has
> > significantly improved
> > between versions 0.9.7 and 0.10.3. Any idea what changed? It
> > seems like for
> > large chunks of python that are getting converted to XML the
> > performance has
> > been drastically improved! Good Job.
> >
> > --Ivan
> >
> > > -----Original Message-----
> > > From: pywebsvcs-talk-admin at lists.sourceforge.net
> > > [mailto:pywebsvcs-talk-admin at lists.sourceforge.net] On Behalf
> > > Of Ivan R. Judson
> > > Sent: Friday, October 31, 2003 8:34 AM
> > > To: 'pywebsvcs'
> > > Subject: [Pywebsvcs-talk] Another way to register objects?
> > >
> > >
> > >
> > > Howdy,
> > >
> > > I'd like to be able to register multiple objects with a
> > > single soap server (I know you can register multiple objects via
> > namespaces), but we've been > doing it by URL path mapping, ie,
> > http://foo.server.com/path/to/object =>
> > server.pathmap[path/to/object] =
> > object.
> >
> > I'm wondering a couple of things:
> >
> > 1) Is this good practice? Is there an alternative that we should be
> > considering?
> > 2) If we add this in the current code do you want it back?
> > 3) should I map the path to a namespace, ie path/to/object =>
> > "path:to:object" and use what's there already?
> >
> > Suggestions, thoughts, comments welcome!
> >
> > --Ivan
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program. Does
> > SourceForge.net help you be more productive? Does it
> > help you create better code? SHARE THE LOVE, and help us help
> > YOU! Click Here: http://sourceforge.net/donate/
> > _______________________________________________
> > Pywebsvcs-talk mailing list Pywebsvcs-talk at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/pywebsvcs-talk
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program. Does
> > SourceForge.net help you be more productive? Does it
> > help you create better code? SHARE THE LOVE, and help us help
> > YOU! Click Here: http://sourceforge.net/donate/
> > _______________________________________________
> > Pywebsvcs-talk mailing list Pywebsvcs-talk at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/pywebsvcs-talk
> >
>
>
> LEGAL NOTICE
> Unless expressly stated otherwise, this message is
> confidential and may be privileged. It is intended for the
> addressee(s) only. Access to this E-mail by anyone else is
> unauthorized. If you are not an addressee, any disclosure or
> copying of the contents of this E-mail or any action taken
> (or not taken) in reliance on it is unauthorized and may be
> unlawful. If you are not an addressee, please inform the
> sender immediately.
>
More information about the ag-dev
mailing list