<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On Mon, Jul 15, 2013 at 8:34 PM, Lucas Holmquist <span dir="ltr">&lt;<a
        moz-do-not-send="true" href="mailto:lholmqui@redhat.com"
        target="_blank">lholmqui@redhat.com</a>&gt;</span> wrote:<br>
    <blockquote
cite="mid:CAD_dpu2H_JynpsfbOtfz7BUw1WK6ujg5r-kC9yxKpsoAHFz8dQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div style="word-wrap:break-word">
                <div>
                  <div class="im">
                    <blockquote type="cite">
                      <div dir="ltr">
                        <div class="gmail_extra">
                          <div class="gmail_quote">
                            <blockquote class="gmail_quote"
                              style="margin:0 0 0 .8ex;border-left:1px
                              #ccc solid;padding-left:1ex">here's a
                              scenario.<br>
                              <br>
                              A user creates an "Application" then adds
                              a new "iOS Variant" to it.<br>
                              <br>
                              they decide they need to rename this
                              Variant since they didn't name it very
                              well.<br>
                              <br>
                              There is currently no way of renaming/
                              updating the description of this variant
                              without re-sending the Certificate/pass
                              phrase. &nbsp;this would be the same for
                              Android and Simple Push, &nbsp;just substitute
                              google key and channels<br>
                            </blockquote>
                            <div><br>
                            </div>
                            <div>Is this really a problem ? Since before
                              an update I assume you do a GET which will
                              contain the Certificate/pass phrase, and
                              then just doing an update passing the
                              whole object again ... I might be missing
                              sometyhing obvious here.&nbsp;</div>
                          </div>
                        </div>
                      </div>
                    </blockquote>
                    <div><br>
                    </div>
                  </div>
                  <div>i have all the info, &nbsp;was hoping to avoid having
                    to resend the certificate/other stuff again.</div>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div style="">Ok I see, with the current model that is not
              really possible (saying trivially) . We could extract all
              this info (cert/pass whatever) into a different
              &nbsp;model/class and just having a 1-1 relation making the
              update on the variant more simple. But I would like to
              have Matzew feedback on this.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    I think the same goes for renaming the Application construct?<br>
    Though it just contains an extra "description" field, so it may not
    be worth it...<br>
    <br>
    Would like to hear Matthew ideas on this as well from an API design
    point of view. :)<br>
    <br>
    Hylke<br>
    <br>
  </body>
</html>