I'm currently working on writing a custom adapter against a large set of APIs that map to multiple models or resources that are quite disparate. From a DM point of view, is there a best practice in handling this type of resource interaction? It seems to me that it might make sense to specify a repository that corresponds to the APIs (say Netflix or what have you) with multiple adapters that correspond to different resources in that repository (in this case, a set of external APIs like user, catalog, titles etc). However, I'm not sure if I'm thinking abstract enough and if there's an alternative approach? Curious to hear feedback.
Cheers, Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
