Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change Receiver/Processor to Application/Connection #6

Closed
germanescobar opened this issue Jun 24, 2011 · 1 comment
Closed

Change Receiver/Processor to Application/Connection #6

germanescobar opened this issue Jun 24, 2011 · 1 comment
Assignees
@germanescobar
Labels
Core Improvement
Milestone
0.3.0

Comments

@germanescobar
Copy link
Contributor

The receiver/processor model has the following problem. Sometimes it's necessary to add a processor in the receivers and a receiver in the processors. The solution is to rename receivers and processors to applications and connections respectively. Applications and connections can have both receivers and processors. Maybe we would want to call them just connectors instead.
germanescobar added a commit that referenced this issue Jun 29, 2011
@germanescobar
Issue #6: Change Receiver/Processor to Application/Connection
1f0f48d 
Instead of ProcessorService and ReceiverService, use only a ConnectorService.
Rename the methods in the RoutingEngine.
Rename everything to applications and connections instead receivers and processors.
@ghost ghost assigned germanescobar Jun 29, 2011
@germanescobar
Copy link
Contributor Author

Done! I did the following changes;

  1. org.mokai.Receiver was renamed to org.mokai.Connector. org.mokai.Processor now extends org.mokai.Connector.
  2. org.mokaiProcessorService and org.mokai.ReceiverService was unified into org.mokai.ConnectorService.
  3. RoutingEngine now has method to manage applications and connections (instead of receivers and processors).
  4. receivers.xml and processors.xml are now named applications.xml and connections.xml (this is parametrizable in the core-context.xml configuration file).
  5. applications.xml and connections.xml both uses the same schema: connectors-0.3.xsd
  6. Re-factored everything accordingly.

germanescobar added a commit that referenced this issue Jul 9, 2011
@germanescobar
Issues #6 and #7
17c583a 
Issue #6: Change Receiver/Processor to Application/Connection.
Issue #7: Should be able to change password.
arcodergh pushed a commit that referenced this issue May 3, 2016
@germanescobar
Issue #6: Change Receiver/Processor to Application/Connection
ef6484f 
Instead of ProcessorService and ReceiverService, use only a ConnectorService.
Rename the methods in the RoutingEngine.
Rename everything to applications and connections instead receivers and processors.
arcodergh pushed a commit that referenced this issue May 3, 2016
@germanescobar
Issues #6 and #7
08c8897 
Issue #6: Change Receiver/Processor to Application/Connection.
Issue #7: Should be able to change password.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@germanescobar germanescobar

Labels
Core Improvement
Projects
None yet
Milestone
0.3.0
Development

No branches or pull requests
1 participant
@germanescobar