On 8/29/16, 1:45 AM, "Greg Dove" <greg.d...@gmail.com> wrote:
>Chris, fyi the BinaryData class is now almost the same as as3 ByteArray >except for the amf part missing: writeObject/readObject and amf0/amf3 >objectEncoding iirc. I think the only other difference is multibyte text >methods missing as well. So it could be a good candidate for adding the >missing amf support to....or perhaps a subclass because I know Alex >mentioned the need to keep lighter options available for 'pay as you go' >approach. Yes, definitely we should keep pay-as-you-go in mind. I was wondering if BinaryData could be used. Sounds like it could be a good starting point. I'd love to see AMF working in JS. I think there is a serious chunk of work in the writeObject/readObject but hopefully it can be encapsulated in beads. I do wonder how well AMF for JS will perform. It certainly would ease migration effort, but performance-wise, it makes the client run the object conversion entirely in JS as opposed to sending some sort of JSON over and having it converted by the browser runtime and then converted to objects. -Alex
