You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Kevin Brown (JIRA)" <ji...@apache.org> on 2008/02/19 03:30:38 UTC
[jira] Created: (SHINDIG-79) Refactor GadgetContext /
ProcessingOptions
Refactor GadgetContext / ProcessingOptions
-------------------------------------------
Key: SHINDIG-79
URL: https://issues.apache.org/jira/browse/SHINDIG-79
Project: Shindig
Issue Type: Improvement
Components: Gadgets Server - Java
Reporter: Kevin Brown
Assignee: Kevin Brown
Priority: Minor
At present, GadgetContext and ProcessingOptions aren't passed consistently throughout the code base. There are many situations where data that is only available in GadgetContext is needed in situations where you only have ProcessingOptions.
I propose eliminating ProcessingOptions and instead moving all this functionality into GadgetContext, with various network layer implementations (HttpContext and RpcContext) working similarly to how they work in ProcessingOptions at present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SHINDIG-79) Refactor GadgetContext /
ProcessingOptions
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Brown closed SHINDIG-79.
------------------------------
Resolution: Fixed
Resolved. yay.
> Refactor GadgetContext / ProcessingOptions
> -------------------------------------------
>
> Key: SHINDIG-79
> URL: https://issues.apache.org/jira/browse/SHINDIG-79
> Project: Shindig
> Issue Type: Improvement
> Components: Gadgets Server - Java
> Reporter: Kevin Brown
> Assignee: Kevin Brown
> Priority: Minor
>
> At present, GadgetContext and ProcessingOptions aren't passed consistently throughout the code base. There are many situations where data that is only available in GadgetContext is needed in situations where you only have ProcessingOptions.
> I propose eliminating ProcessingOptions and instead moving all this functionality into GadgetContext, with various network layer implementations (HttpContext and RpcContext) working similarly to how they work in ProcessingOptions at present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.