On Thu, Aug 13, 2009 at 2:25 AM, ob1.data<[email protected]> wrote:
>
> I'm a newbie, so don't quote me on this but I think I read somewhere
> that JSON does not scale well. So I think the alternative of using
> XML encoding to serialize might be better.
that isn't really true. Almost every json string will be smaller than
the XML equivalent. The only exception is some deformation (which by
the way somehow breaks the idea of XML) that some protocols do, for
example the webservices defined by WSGI have some "optimization" where
you can extract a set of the XML and replace it with a reference then
put that set below in the XML stream which saves you space because the
block of code is only one time in the steam and you have several
references to it. That in itself has two mayor problems.
1- It break the concept that XML is human reable, because it breaks
the flow and more importantly
2- It means your data model is broken! Why do you want to store the
same information twice in the same stream??
> Also, I think you need
> Elixir installed on top of SQLAlchemy to handle M:N relationships in
> the traditional fashion. Then maybe it'd be simpler.
huh? have you used sa declarative? I think you are confusing active
record (what you call traditional) with "data mapper ("SA's way")
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
