jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Gomes Rodrigues <ra0...@gmail.com>
Subject Re: JMX size (was svn commit: r1736119 - /jmeter/trunk/src/components/org/apache/jmeter/visualizers/backend/BackendListener.java)
Date Fri, 25 Mar 2016 15:19:13 GMT
Ok no problem

Thank to your clear answer

Cet e-mail a été envoyé depuis un ordinateur protégé par Avast.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2016-03-25 14:32 GMT+01:00 sebb <sebbaz@gmail.com>:

> On 25 March 2016 at 12:42, Antonio Gomes Rodrigues <ra0077@gmail.com>
> wrote:
> > Hi Sebb,
> >
> > Thanks to your quick answer, now it's more cleare to me
> >
> > If file size is a problem, I don't think to keep xml format is a good
> idea
>
> I didn't write that size was a problem, merely that not saving
> defaults means smaller files.
> [Though of course this only applies to the default cases]
>
> Besides, I don't think there's much wasted text in the JMX format.
> And there is a very good library for reading it (XStream).
>
> XStream has lots of useful features including aliasing.
> for example, guiclass="ThreadGroupGui" actually instantiates
> org.apache.jmeter.threads.gui.ThreadGroupGui
>
> Remember that the JMX file has to be unpacked into Java classes with
> all their fields.
>
> Also of course changing the format would break compatibilty.
> There would have to be *compelling* reasons for doing so.
> It would be a lot of work for developers and a lot of changes for users.
> And it would break some 3rd party products.
>
> > Antonio
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message