Comments on: Saving User preferences on the server – cutting corners in Flex http://flexblog.faratasystems.com/2006/12/21/bringing-together-sharedobject-bytearray-and-dynamic-typing-in-flex A blog about our experience with Adobe Flex Tue, 31 Jan 2012 19:52:28 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Yakov http://flexblog.faratasystems.com/2006/12/21/bringing-together-sharedobject-bytearray-and-dynamic-typing-in-flex/comment-page-1#comment-1218 Yakov Sun, 24 Dec 2006 13:03:21 +0000 http://flexblog.faratasystems.com/?p=141#comment-1218 While Java developers do not consider XML as the only serialization format, XML is being abused in J2EE world as the only way of configuring multiple frameworks to make them work together. I've been writing on the subj on multiple ocasions, and this is the most recent article: http://java.sys-con.com/read/299903.htm While Java developers do not consider XML as the only serialization format, XML is being abused in J2EE world as the only way of configuring multiple frameworks to make them work together. I’ve been writing on the subj on multiple ocasions, and this is the most recent article: http://java.sys-con.com/read/299903.htm

]]> By: Valery Silaev http://flexblog.faratasystems.com/2006/12/21/bringing-together-sharedobject-bytearray-and-dynamic-typing-in-flex/comment-page-1#comment-1217 Valery Silaev Sun, 24 Dec 2006 12:20:02 +0000 http://flexblog.faratasystems.com/?p=141#comment-1217 Anatole, I believe that I understand Yakov's point correctly. The only thing I'd like to emphasize is that Yakov grants too much to "open-mind thinking" of Java crowd (and I'm part of this crowd). EJB + XML descriptors, Spring + XML configurations, Hibernate + XML mappings... JavaScript developers at least know about JSON alternative, Ruby developers consider YAML, Java developers stick with XML for all cases (configuration, preferences, transport formats). So 90% of Java Joe-s never get to the static vs dynamic aproaches comparision while they take different direction on previous step -- XML as the only possible serialization format. They will advocate that this is a "standard" solution and, ironically, they will be right -- they refer to standard set by Sun+IBM+BEA+...numerous OSS projects. VS Anatole,

I believe that I understand Yakov’s point correctly. The only thing I’d like to emphasize is that Yakov grants too much to “open-mind thinking” of Java crowd (and I’m part of this crowd). EJB + XML descriptors, Spring + XML configurations, Hibernate + XML mappings… JavaScript developers at least know about JSON alternative, Ruby developers consider YAML, Java developers stick with XML for all cases (configuration, preferences, transport formats).

So 90% of Java Joe-s never get to the static vs dynamic aproaches comparision while they take different direction on previous step — XML as the only possible serialization format. They will advocate that this is a “standard” solution and, ironically, they will be right — they refer to standard set by Sun+IBM+BEA+…numerous OSS projects.

VS

]]> By: Anatole Tartakovsky http://flexblog.faratasystems.com/2006/12/21/bringing-together-sharedobject-bytearray-and-dynamic-typing-in-flex/comment-page-1#comment-1189 Anatole Tartakovsky Sat, 23 Dec 2006 15:09:14 +0000 http://flexblog.faratasystems.com/?p=141#comment-1189 Valera, Interesting comment. I think Yakov's point was to show the difference in thinking in scripting languages: (1-liners approach) versus strong-typing-compiler-knows-everything one. Syntax "compatibility" of ActionScript and Java cause people to use the same code and techniques. Two points, really: 1 not to use classes as Object is quite flexible and should not be treated as sunctional compatibility. 2. serialization / deserialization in Flex are way different from Java. XML deep copy serializer would make sense for some applications requiring both sides persistance and accessibility. However, I think for the most cases we would advocate rpc calls for simplicity Thank you Anatole Valera,
Interesting comment. I think Yakov’s point was to show the difference in thinking in scripting languages: (1-liners approach) versus strong-typing-compiler-knows-everything one. Syntax “compatibility” of ActionScript and Java cause people to use the same code and techniques. Two points, really:
1 not to use classes as Object is quite flexible and should not be treated as sunctional compatibility.
2. serialization / deserialization in Flex are way different from Java.

XML deep copy serializer would make sense for some applications requiring both sides persistance and accessibility. However, I think for the most cases we would advocate rpc calls for simplicity

Thank you
Anatole

]]> By: Valery Silaev http://flexblog.faratasystems.com/2006/12/21/bringing-together-sharedobject-bytearray-and-dynamic-typing-in-flex/comment-page-1#comment-1148 Valery Silaev Fri, 22 Dec 2006 11:00:08 +0000 http://flexblog.faratasystems.com/?p=141#comment-1148 You say "not exactly object-oriented"? Hehe... The first suggestion from Java camp will be not about OOP, but rather about using XML as preferences format :) Sure, shortly they suggest you to roll your own ActionScript JAXB atop of this ;) VS You say “not exactly object-oriented”?

Hehe…

The first suggestion from Java camp will be not about OOP, but rather about using XML as preferences format :)
Sure, shortly they suggest you to roll your own ActionScript JAXB atop of this ;)

VS

]]>