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.

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

Develop a bi-directional TransformConnector #61

Closed
dgeb opened this issue Oct 8, 2014 · 1 comment
Closed

Develop a bi-directional TransformConnector #61

dgeb opened this issue Oct 8, 2014 · 1 comment

Comments

@dgeb
Copy link
Member

dgeb commented Oct 8, 2014

This will allow for sources to ignore didTransform events raised by the other while transforms are being applied. This could eliminate the need for many sources to maintain caches.

Possible approaches:

  • make two uni-directional connectors aware of each other
  • create a separate bi-directional connector that encapsulates two uni-directional connectors
  • create a completely separate bi-directional connector
@dgeb
Copy link
Member Author

dgeb commented Mar 2, 2015

With the introduction of transformation tracking in #96, I don't believe that there is still a need for a bi-directional TransformConnector.

@dgeb dgeb closed this as completed Mar 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant