[
https://issues.apache.org/jira/browse/SHINDIG-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600339#action_12600339
]
David Primmer commented on SHINDIG-268:
---------------------------------------
In reponse to your general comment above:
I don't share your lack of faith in Abdera. It's been hard to get interest in
this particular subject, but they've been very responsive throughout this
project to our needs and fixed bugs and changed functionality within a day or
so of our requests. James Snell was trying to work on this today when Jira blew
up.
So I don't agree that we should add this code in addition to the many hours of
workarounds we've already done on this issue before a cursory look from James.
Much of the work I've done on this project has been around this RouteManager
object and I know it pretty well now and when I originally proposed the enum, I
had a feeling that it really should have been a fix for the RouteManager but
took the quick path. From my perspective, we're doing hacks on top of hacks for
this particular feature. If we spent just a few of the brain cycles we've spent
on writing this new shindig only Route Managment system instead of improving
the fairly simple Abdera Route system, there's be a lot less code checked into
Shindig and abdera would be more useful.
It seems from your comment that removing old code is the primary driver for
this. Can't we focus on some new features for a few days instead?
> Refactor Route managment in the provider
> ----------------------------------------
>
> Key: SHINDIG-268
> URL: https://issues.apache.org/jira/browse/SHINDIG-268
> Project: Shindig
> Issue Type: Improvement
> Components: RESTful API (Java)
> Reporter: David Primmer
> Attachments: exampleUsage.txt,
> shindig-268_refactor_route_managment.patch, useGuiceForRoutes.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
