[jboss-jira] [JBoss JIRA] (WFLY-1576) Trim information coming from read-resource-description

[jaikiran pai (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai updated WFLY-1576:
-------------------------------

        Summary: Trim information coming from read-resource-description  (was: Trim infornation coming from read-resource-description)
    Description: 
17:00 hbraun
but the ability to reduce the payload size (removing unwanted meta data), would certainly be useful
17:01
did you do a comparison how many bytes we added per attribute?
17:01 kkhan
no?
17:02 hbraun
me neither 
17:02 kkhan
still we don't include operations by default
17:02
we don't do recursive by default
17:02
including the access-control runtime state will be configurable
17:02
what else do you want to remove?
17:03 hbraun
"nillable" => false ?
17:03
storeage ?
17:03
nillable=false: the boolean is false by default
17:03
storage is not needed at all
17:03
access-type is not needed at all (client side)
17:04
"restart-required" is not needed so far
17:04 kkhan
aha, so that is what you were talking about
17:04 hbraun
yes
17:04 kkhan
I think cli needs some of thos
17:04
e
17:04 hbraun
all that rubbish bloats the reponse payload size, w/o clients making actual use of that
17:05 kkhan
ok, I'll keep that in mind but will do the real task first
17:05 hbraun
well, we drive by a parameter: extended=true
17:05
sure
17:05
tnx
17:05 kkhan
an additional parameter like trim-values=[storage,nillable,access-type] or something should do the job
17:06
to read-resource-description
17:06 hbraun
or we do simpe default and extended scopes
17:06
two should suffice
17:06
additional parsing of trim-values[] adds overhead as well
17:07 kkhan
Not really in comparison to what goes on inside these ops
17:07 hbraun


  was:

17:00 hbraun
but the ability to reduce the payload size (removing unwanted meta data), would certainly be useful
17:01
did you do a comparison how many bytes we added per attribute?
17:01 kkhan
no?
17:02 hbraun
me neither 
17:02 kkhan
still we don't include operations by default
17:02
we don't do recursive by default
17:02
including the access-control runtime state will be configurable
17:02
what else do you want to remove?
17:03 hbraun
"nillable" => false ?
17:03
storeage ?
17:03
nillable=false: the boolean is false by default
17:03
storage is not needed at all
17:03
access-type is not needed at all (client side)
17:04
"restart-required" is not needed so far
17:04 kkhan
aha, so that is what you were talking about
17:04 hbraun
yes
17:04 kkhan
I think cli needs some of thos
17:04
e
17:04 hbraun
all that rubbish bloats the reponse payload size, w/o clients making actual use of that
17:05 kkhan
ok, I'll keep that in mind but will do the real task first
17:05 hbraun
well, we drive by a parameter: extended=true
17:05
sure
17:05
tnx
17:05 kkhan
an additional parameter like trim-values=[storage,nillable,access-type] or something should do the job
17:06
to read-resource-description
17:06 hbraun
or we do simpe default and extended scopes
17:06
two should suffice
17:06
additional parsing of trim-values[] adds overhead as well
17:07 kkhan
Not really in comparison to what goes on inside these ops
17:07 hbraun



    
> Trim information coming from read-resource-description
> ------------------------------------------------------
>
>                 Key: WFLY-1576
>                 URL: https://issues.jboss.org/browse/WFLY-1576
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Kabir Khan
>            Assignee: Brian Stansberry
>
> 17:00 hbraun
> but the ability to reduce the payload size (removing unwanted meta data), would certainly be useful
> 17:01
> did you do a comparison how many bytes we added per attribute?
> 17:01 kkhan
> no?
> 17:02 hbraun
> me neither 
> 17:02 kkhan
> still we don't include operations by default
> 17:02
> we don't do recursive by default
> 17:02
> including the access-control runtime state will be configurable
> 17:02
> what else do you want to remove?
> 17:03 hbraun
> "nillable" => false ?
> 17:03
> storeage ?
> 17:03
> nillable=false: the boolean is false by default
> 17:03
> storage is not needed at all
> 17:03
> access-type is not needed at all (client side)
> 17:04
> "restart-required" is not needed so far
> 17:04 kkhan
> aha, so that is what you were talking about
> 17:04 hbraun
> yes
> 17:04 kkhan
> I think cli needs some of thos
> 17:04
> e
> 17:04 hbraun
> all that rubbish bloats the reponse payload size, w/o clients making actual use of that
> 17:05 kkhan
> ok, I'll keep that in mind but will do the real task first
> 17:05 hbraun
> well, we drive by a parameter: extended=true
> 17:05
> sure
> 17:05
> tnx
> 17:05 kkhan
> an additional parameter like trim-values=[storage,nillable,access-type] or something should do the job
> 17:06
> to read-resource-description
> 17:06 hbraun
> or we do simpe default and extended scopes
> 17:06
> two should suffice
> 17:06
> additional parsing of trim-values[] adds overhead as well
> 17:07 kkhan
> Not really in comparison to what goes on inside these ops
> 17:07 hbraun

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira