Comments for JacksonDunstan.com

Comment on AMF Serialization Tricks by jackson

jackson — Tue, 21 May 2013 00:17:29 +0000

That's a really good point. Since you're not sending standard AMF for any class you implement IExternalizable for, you'll need to do the same custom deserialization in any code (e.g. server) that handles the serialized data, if any.

Comment on AMF Serialization Tricks by Mike Keesey

Mike Keesey — Mon, 20 May 2013 22:33:30 +0000

Of course this also means that your server component must replicate the same serialization logic (unless you just plan to used it for SharedObject storage or something).

Comment on Faster Logic With Bitwise Operators by aconma

aconma — Mon, 20 May 2013 05:40:24 +0000

Of course. The environment of the test above:

- AIR SDK 3.4 for desktop (extended desktop only), compiling in release mode (no debugging or verbose stack traces)
- Release version of Flash Player 11.4
- 2.3 Ghz Intel Core i3
- Windows 7 Ultimate 32Bit (6.1 Build 7600)

And other test, run in Flash Player 11.4 only (no debugging and tracing)

Test,&& Time,& Time
1-false,300,277
5-false,613,277
10-false,1051,292
1-true,313,266
5-true,395,276
10-true,690,280
1-null,281,277
5-null,614,290
10-null,1100,276
1-not null,309,276
5-not null,910,275
10-not null,2080,277

Comment on Faster Logic With Bitwise Operators by jackson

jackson — Sun, 19 May 2013 18:18:37 +0000

Interesting results. Can you share more information about the compile and runtime environment you tested with? For example, was this AIR for Windows, Mac, iOS, or Android? Which device and with what specs? What compiler and with what settings?

Comment on Faster Logic With Bitwise Operators by aconma

aconma — Sun, 19 May 2013 09:10:28 +0000

I mean: above

Comment on Faster Logic With Bitwise Operators by aconma

aconma — Sun, 19 May 2013 09:07:03 +0000

First, sorry for my poor English.
Please note that the result abow is only true if you run this code in Flash Player only (For example: browser)
If you complie and run in AIR, the result is:

Test,&& Time,& Time
1-false,313,1104
5-false,757,2207
10-false,1216,3716
1-true,312,1155
5-true,315,2263
10-true,665,3713
1-null,312,1143
5-null,355,2172
10-null,1249,3730
1-not null,309,1067
5-not null,937,2255
10-not null,2107,3724

(I editted comment for spelling reason)

Comment on Why Objects Serialized With ByteArray Are So Small by jackson

jackson — Tue, 14 May 2013 16:15:05 +0000

I’ve used it, but haven’t yet written any articles about it. I’ll make a note to do a followup article.

Comment on Why Objects Serialized With ByteArray Are So Small by Michal Wroblewski (@wrobel221)

Michal Wroblewski (@wrobel221) — Tue, 14 May 2013 07:50:47 +0000

By byte orded I meant endian. So when calling writeObject it will be encoded in AMF, right? Before that I'll set endian and I'm ready to go. I suppose I should use registerClassAlias with that. Much thanks Jackson

Comment on Why Objects Serialized With ByteArray Are So Small by MikeA

MikeA — Tue, 14 May 2013 05:49:09 +0000

Have you tried playing with the IExternalizable interface? That allows you to define how you want an object to be read from and written to a byte stream. I’ve only used it for objects that store atomic data (ints, Numbers, Strings), but it’d be interesting to see if it does the same object referencing that writeObject does for generic Objects.

Comment on Why Objects Serialized With ByteArray Are So Small by jackson

jackson — Mon, 13 May 2013 20:30:44 +0000

AMF is portable between the various platforms that Flash supports (desktop browser, iOS, Android, etc.) and is even available on some other platforms, such as Java with Adobe's BlazeDS and PHP with AMFPHP. You shouldn't have problems with byte order, but you probably want to make sure you use a consistent ByteArray.endian setting.