Perhaps supporting optional alias registration for types (case classes) could be a way to reduce domain coupling. It could be used to provide a level of abstraction. Granted it's more work to initialize so there are drawbacks.
On Oct 17, 4:40 am, Marius <marius.dan...@gmail.com> wrote: > Hmmm ... I wonder if heterogeneous lists should be supported. I also > wonder if type knowledge in JSON is a good thing to do as it seems to > me that we're bringing knowledge from another domain creating > couplings. I'm not sure if there is a different way to solve this ... > it just doesn't feel completely right to me ... but this doesn't > necessarily mean it is not right :) > > Br's, > Marius --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
