Hao Wu
Hao Wu
We are aware of this and will be in our roadmap, but we just don't have enough justifications yet to prioritize this at this point. Stay tuned!
@brettfazio FYI.
It is definitely possible to allow connecting to other hosts, the `EDOHostPort` was abstracted to locate the host, whether it's a device, another machine, or a local machine. We don't...
Yes. There wasn't an issue to not use `NSSecureCoding` but only for a quick serialization solution. If you have better solutions, any PR is welcomed!
can you provide how `NSXPCConnection` handles async callback, API etc? when you mentioned block, you mean the actual `block` type, the anonymous function, right? eDO doesn't have `future` but can...
> `- (void)upperCaseString:(NSString *)aString withReply:(void (^)(NSString *))reply;` are you saying that you declare your own method signature where you have a callback block? then in your impl in the server...
>I only declare a protocol. Did you declare the last `reply:` in your protocol as well? > Regarding +load, +initialize and attr(constructor), I've hit similar issues of order. Thanks for...
but that only matters after the block is invoked remotely? as long as by the time you invoke a remote block, the attr(constructor) is set, you should be good, right?
Oh I see. Let's continue the discussion on a different thread, and focus on the async call for this one. Both look like legitimate issues to resolve to me.
oh so you are saying, Apple forces the method to be a pattern that has a `reply:` in the end with the return value as its argument?