perfsonar development work

[Jochen Reinwand <>]

Hello Maciej,

On Thursday 05 April 2007 15:39, Maciej Glowiak wrote:
> I have similar impression how the client API should look like.

From the examples you gave I can see that what you have in Java and also what 
you're planning to do is really exactly what I had in mind ;-)
I wonder what the problem was during the discussion in Utrecht...

> There are NMWG classes for Message construction and Axis functionality
> for SOAP. Unfortunately Axis uses DOM Document to store date, so our
> NMWG "DOM representation" must be converted into DOM Document. That's
> the performance issue to be resolved in the future.

Yes, DOM can cause performance problems... Seems like the Perl implementation 
of SOAP uses its own parsers. Perhaps they encountered similar problems by 
just using some DOM module. But we are also using DOM for our perfSONAR Perl 
implementation. So far the performance seems to be acceptable. The DOM 
implementation we're using is more or less the Perl interface to the standard 
Open Source C/C++ XML library libxml. This library seems to be quite fast and 
C/C++ always tends to be faster than Java ;-)

But, anyway, seems like there is no "disagreement" on API design itself. So 
we 
can most likely close this discussion.

I'm still thinking about using the Java extension of Perl to directly use the 
perfSONAR classes from within our Perl code...

greetings,
Jochen

-- 
Jochen Reinwand                                 Tel: +49 9131 852-8689
DFN Labor

Regionales Rechenzentrum Erlangen
Martensstrasse 1
91058 Erlangen
 
email: