Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(542)

Issue 4748053: Avoid dual-mode deferred (and immediate) export JS processor

Can't Edit
Can't Publish+Mail
Start Review
Created:
14 years, 8 months ago by mhermanto
Modified:
14 years, 8 months ago
Reviewers:
johnfargo, fargo
Base URL:
http://svn.apache.org/repos/asf/shindig/trunk/
Visibility:
Public.

Description

Each processor is concrete in what it does, ie: no more this.getXXXInstance(). Better for overidability.

Patch Set 1 : update #

Patch Set 2 : update #

Total comments: 1

Messages

Total messages: 2
mhermanto
14 years, 8 months ago (2011-07-18 19:07:26 UTC) #1
johnfargo
14 years, 8 months ago (2011-07-18 22:04:06 UTC) #2
LGTM++

Thanks, this is much better.

http://codereview.appspot.com/4748053/diff/9001/java/gadgets/src/main/java/or...
File
java/gadgets/src/main/java/org/apache/shindig/gadgets/js/DeferredExportJsProcessor.java
(right):

http://codereview.appspot.com/4748053/diff/9001/java/gadgets/src/main/java/or...
java/gadgets/src/main/java/org/apache/shindig/gadgets/js/DeferredExportJsProcessor.java:63:
featureRegistry = featureRegistryProvider.get(jsUri.getRepository());
for later, we might consider adding this to JsRequest itself, since we now
precompute the requested/new/existing list there as well (it's a common
pattern).
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b