I cannot provide sample code because I don't have a clear idea how the API could look.
Think about the role that a ORM is playing. What I want to understand is what would a functional equivalent would look like in Elm. What would sit above graphQL or REST or some other lower level tech? Another way to look at this would be to take the Json.Decode/Encode as example and imagine that one has the equivalent of a Decoder only that it would be some kind of a descriptor used by some lower level library that does the queries based on that descriptor data. Maybe this descriptor uses something like Datalog. Another way to think about this is to try to imagine what would it take to reduce the cognitive overload of a beginner that does not really care that much about how the data is retrieved/saved remotely but cares to have the functionality present. On Mon, Oct 24, 2016 at 11:01 PM, John Kelly <[email protected]> wrote: > On Monday, October 24, 2016 at 8:33:55 AM UTC-7, Peter Damoc wrote: >> >> I'm more interested in how one would solve this in a multilayer system >> where the actual remote persistence is abstracted from the app. >> >> The actual remote persistence might be implemented with REST, or it might >> be some kind of websockets thing. >> It might involve a SQL database, or maybe a NoSQL database. >> It might be something like Datomic. >> >> I'm interested in how would one implement this abstraction, this *separation >> of concerns*. >> > > Could you provide more details of what you are looking for? Or some sample > code? > > Are you interested in how one would abstract away the data consumption? > What I mean by that is: The library user simply requests data and the > library determines if it needs to make an API call or if it can just get > the data from localStorage. > > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- There is NO FATE, we are the creators. blog: http://damoc.ro/ -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
