perfsonar development work

[Roman Lapacz <>]

Maciej Glowiak wrote:
> > conversion to NMWG takes more than linear time (and I would expect it 
> > to be better than linear) I think concentrating on it here is 
> > misplaced. If you read the previous threads we have discussed this 
> > topic several times.
> >
> > If I'm not mistaken, we all agree for the case of the LS conversion 
> > to nmwg is less efficient. However, there are many other cases where 
> > it is more efficient. (Especially if you don't convert to DOM at 
> > all.) Unless 
>
> Now, with our generic we can't do it. All messages are parsed into DOM 
> first and we don't have any influence on it (because it's inside Axis).

I remember that Martin proposed to solve the problem with handlers in 
Axis (I don't know these handlers at all but my understanding is that 
they can change the behavior  and some internal conversions in Axis).

> > Then, for other message types the nmwg classes could still be used - 
> > because for many of them it is more efficient and much more easy to 
> > use and understand.
> >
> > > 3. Another significant time (which wasn't measured here directly, 
> > > sorry)
> > >    is initialization of eXist DB XML StorageManager. In Tomcat this
> > >    StorageManager is initialized only once.
> > >
> > > 4. The most significant time is querying the eXist DB server. We can't
> > >    speed it up with old StorageManager which uses XML:DB for communi-
> > >    cation (default way of communication to DB server from Java), so I
> > >    wrote new HTTP access to the DB server which is much faster for
> > >    smaller queries. Additional tests will be provided soon, but it's
> > >    already on SVN repository
> >
> > Is there any downside? What functionality is provided by XML:DB that 
> > is not provided by your HTTP access? Do we care about any of that 
> > functionality? This sounds like really good, useful work to me. But, 
> > I would like to know what (if anything) we are giving up.
>
> Hmm, I think there is no downside. We use only basic communication to 
> the eXist DB. XML:DB is Java API for accessing XML databaseses. It's a 
> common way. Recently I read a discussion on eXist wiki on this topic. 
> Someone asked why eXist DB Java API used XML:DB which was not so easy 
> to use. The answer was that it was a standard which should be followed.

Remember that we might need some day encrypted communication between the 
service and eXist. That new http implementation will have to support it.


Roman