Revamping this has been on my todo list since the first version of these
classes. I don't think any radical changes need to be made, but there
needs to be a way of decoupling the provider implementation from the URL
context. Instead of entry.addLink(...), I should be able to do thing
like entry.addLink(context.getUrlFor(entry, "edit")) or whatever.
- James
Dan Diephouse wrote:
> I'm looking into ways to simplify server side APP development with
> Abdera a bit. One of the issues that has posed a problem is that often
> knowledge of how your URLs are mapped seem to reside in both the
> resolver and the Provider. Even in the "simple" example, we have things
> like:
>
> Collection collection = workspace.addCollection("Simple", "atom/feed");
>
> OR
>
> entry.addLink("feed/" + entry.getId().toString(), "edit");
>
> How are other people handling this? Are people hard coding their URL
> strucutre into the actual Provider? Does any one have any ideas on how
> to better integrate the two concepts so that I need to need to let both
> my resolver and my provider know about the URL structure?
>
> Maybe I just need to write a custom Resolver which delegates to my
> Provider?
>
> Cheers,
> - Dan
>
