Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Michael A. Labriola" <labriola@digitalprimates.net>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Subject: RE: RFC - additional registerClassAlias
Thread-Topic: RFC - additional registerClassAlias
Thread-Index: 
 Ac0TbSAqh5N4jQEBTpKqkIO4ZD9TXgAAfO8dAAALN+AAAC/MygAACRHQAADGgU8AAR1h8AAAtOEA
Date: Thu, 5 Apr 2012 22:25:18 +0000
Message-ID: 
 <EB6F7A48D477254EAB8F675582F80CD72673405F@DPSBS1.digitalprimates.local>
References: 
 <EB6F7A48D477254EAB8F675582F80CD726733C6E@DPSBS1.digitalprimates.local>
 <CBA35CE3.3EB8C%aharui@adobe.com>
 <EB6F7A48D477254EAB8F675582F80CD726733DBA@DPSBS1.digitalprimates.local>
In-Reply-To: 
 <EB6F7A48D477254EAB8F675582F80CD726733DBA@DPSBS1.digitalprimates.local>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

>For now, are you okay with adding this to VectorList and then going from t=
here?

I could do this by noticing the type of the Vector when a VectorList is ins=
tantiated or when you attempt to serialize, but there is a catch. If I rece=
ive a Vector from the server before the first time a VectorList is instanti=
ated, the serialization will fail. That's a crappy thing to debug as multip=
le paths through an application could yield different results.=20

I could also do it as a static initializer of the VectorList class so that =
the first time the class is touched the register happens. Still not ideal, =
but at least you would only pay if you used the VectorList.

Thoughts?
Mike