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

can far category #10

Open
Speedy37 opened this issue Sep 29, 2017 · 0 comments
Open

can far category #10

Speedy37 opened this issue Sep 29, 2017 · 0 comments
Assignees
Milestone

Comments

@Speedy37
Copy link
Contributor

The current spec about far category raise a problem to implement some classes.

For example, the datasource interface save method always does some work locally before calling the real far method distantSave. Both calls uses the same syntax but there is no difference in how they are declared and the parameters behaviors isn't the same.

So a new kind of category must be introduced to still mark "can call a far method" methods: canFarCategory.

The far* invocation methods are renamed inv* and can call far, canFar methods

@Speedy37 Speedy37 added this to the 0.8 milestone Oct 11, 2017
@Speedy37 Speedy37 self-assigned this Oct 11, 2017
@Speedy37 Speedy37 removed the spec label Oct 18, 2017
@Speedy37 Speedy37 added the core label Nov 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant