Re: [Pywebsvcs-talk] Hello to all ZSI users

[Marco B. <mar...@gm...>]

Hello, Stanley; I'm putting my reply between your lines.

On Mon, Nov 28, 2011 at 6:51 PM, Stanley A. Klein <sk...@cp...> wrote:

> It seems to me that there are some major improvements that could be
> considered for ZSI.
>


Yes; at the moment, my priority is to fix the standing bugs so that, at
least:

- tests run 100%;
- known bugs are fixed.

Once I'm done with that, I'd like to move to some small scale and wide
scale refactorings.





>
> 1.  Since the last ZSI release there have been some packages released that
> could possibly improve performance and simplify the code needed to be
> developed by the ZSI user.  These include traits (that provides type
> enforcement and appears mappable to WSDL object definitions), lxml (that
> supports the ElementTree Python XML functionality and provides other
> potentially useful features), and GenerateDS (that parses an XML schema
> and generates related Python data structures).  A rebuild of ZSI based on
> these packages might be worth considering, although it would involve major
> surgery on the code.
>
>


Agreed with lxml; I think there is some patch in SF to use lxml in ZSI,
even though it had some problems (I should check, I don't remember the
details).

I'm not very much into putting a new library per se; there are functions
which are missing at the moment (handling of multipart/related and
dime-encoded, for example), and use of packages which are marked as
deprecated (like multifile, deprecated in python2.5). I'd like to clean
those first.




> 2.  There now is (or will soon be) a W3C standard called Efficient XML
> Interchange (EXI).  EXI will greatly improve over-the-wire performance for
> SOAP-based communications.  Right now all EXI implementations are in Java.
>  It might be possible to integrate EXI into ZSI message generation so
> instead of producing XML, converting to EXI for transmission, receiving
> the EXI, and converting to XML on reception, the EXI could be produced
> directly within ZSI and parsed and converted to XML by ZSI on reception.
> There are at least two aspects of EXI, one involves efficient coding of
> frequently used strings (many of which could be determined from the WSDL),
> and the other is a zip-like compression (that might be implemented by
> modifying the code of a zip compressor).
>

Not looked at EXI yet; as I said, before implementing other standards, I'd
like to complete the implementation of those already on the way.



>
> 3.  Parts of ZSI perform what amounts to string templating.  IIRC,
> following the ZSI release, templating was included in the Python language.
>  Some improvements might be achieved by updating the ZSI code to a more
> recent version of Python.
>



Can you elaborate on the templating?

As for the version, yes, I'd like to use some of the latest features of
python; however, I'd like to know the status of current users, as for the
versions they are using; for example, I'm somehow forced to use something
between python 2.3 and python 2.4 (even though I'm making the tests
primarly on python 2.6, for the moment). I don't want to throw out of the
window those who are still using ZSI.



>
> I know these are potentially major changes, but I think they would bring
> ZSI much more up to date.  I also think these may be very useful
> improvements for future use.  I hope this helps.
>



All suggestions are welcome, at the moment :D



>
>
> Stan Klein
>
>
> On Mon, November 28, 2011 10:31 am,  Marco Bizzarri
> <mar...@gm...> wrote:
>
> > Date: Thu, 24 Nov 2011 14:02:58 +0100
> > From: Marco Bizzarri <mar...@gm...>
> > Subject: [Pywebsvcs-talk] Hello to all ZSI users
> > To: pyw...@li...
> > Message-ID:
> >       <
> CAH...@ma...>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > Hi all.
> >
> > I've recently joined the group of ZSI developers; I'd like to release
> > quite
> > soon (possibly within the next week) a new alpha release of ZSI 2.1. I'd
> > like to hear from the current users of ZSI the bug they still find in ZSI
> > and the new features they would like to see included in the 2.1 release.
> > As
> > for me, I'd like the following two (since I've to use them in a couple of
> > projects):
> >
> > - Soap with Attachments support, both for the client and for the server;
> > - DIME encapsulation;
> >
> > As for the second one, I've an (admitedly ugly) implementation of the
> > feature I'd like to share with the others. However, I'll include it in
> the
> > next alpha, since now I would like to tag the current code as alpha 2.
> >
> > Please let me know your thoughts.
> >
> > Regards
> > Marco
>
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Pywebsvcs-talk mailing list
> Pyw...@li...
> https://lists.sourceforge.net/lists/listinfo/pywebsvcs-talk
> Also archived at http://groups.google.com/group/pywebsvcs
>



-- 
Marco Bizzarri
http://code.google.com/p/qt-asterisk/
http://notenotturne.blogspot.com/
http://iliveinpisa.blogspot.com/