Re: I need some feedback

2019-01-24 Thread Jens Alfke
> On Jan 24, 2019, at 7:04 AM, Howard Shere > wrote: > > Anyone have any experience trying this out? > > https://github.com/devsisters/libquic QUIC is pretty bleeding-edge, part of Google’s post-HTTP2 experiments with pushing browser performance. If

Re: I need some feedback

2019-01-24 Thread Howard Shere
Anyone have any experience trying this out? https://github.com/devsisters/libquic On Jan 18, 2019, at 3:04 PM, Quinn The Eskimo! mailto:eski...@apple.com>> wrote: CAUTION: This email originated from outside of Synchronoss. On 18 Jan 2019, at 17:33, Howard Shere

Re: I need some feedback

2019-01-21 Thread Adam Kaplan
Having also implemented WebSockets to spec in the past, I agree that people shouldn’t be doing that. Too many edge cases to handle, like a single UTF-16 character split across frames and other madness. Luckily there are some great WebSocket projects like Starscream (

Re: I need some feedback

2019-01-18 Thread Josh Graessley
> On Jan 18, 2019, at 3:18 PM, Jens Alfke wrote: > > > >> On Jan 18, 2019, at 1:04 PM, Quinn The Eskimo! > > wrote: >> >> Implementing TLS for a peer-to-peer product like this one is not without its >> challenges, > > It would be easy, if Apple provided a

Re: I need some feedback

2019-01-18 Thread Jens Alfke
> On Jan 18, 2019, at 1:04 PM, Quinn The Eskimo! wrote: > > Implementing TLS for a peer-to-peer product like this one is not without its > challenges, It would be easy, if Apple provided a WebSocket API. I really, really wish Apple would provide one. (And yes, I did file a Radar requesting

Re: I need some feedback

2019-01-18 Thread Quinn "The Eskimo!"
On 18 Jan 2019, at 17:33, Howard Shere wrote: > The code is currently using CommonCrypto … CommonCrypto will do a good job of each specific crypto algorithm, but network security depends on how you assemble those algorithms into a protocol. That’s very hard to do correctly, even by security

Re: I need some feedback

2019-01-18 Thread Howard Shere
The code is currently using CommonCrypto, just looking at all my options before I rewrite the transport (which I inherited from previous developers). On Jan 18, 2019, at 11:30 AM, Jens Alfke mailto:j...@mooseyard.com>> wrote: CAUTION: This email originated from outside of Synchronoss. On

Re: I need some feedback

2019-01-18 Thread Jens Alfke
> On Jan 17, 2019, at 12:26 AM, Quinn The Eskimo! wrote: > > Finally, a question: Is there a reason you’re doing your own encryption > rather than using TLS? Creating your own on-the-wire crypto is very tricky, > and it’s something best left to the experts. +1. This is fraught with peril.

Re: I need some feedback

2019-01-17 Thread Quinn "The Eskimo!"
On 16 Jan 2019, at 20:32, Howard Shere wrote: > We can’t entirely stream from the files because we need to encrypt the data. H. I have various points on that front: * The networking APIs don’t generally support a “send this file to this connection” primitive, so you have to read the

Re: I need some feedback

2019-01-16 Thread 孔祥波
CommonCrypto good enough , iOS/macOS have hardware accelerate. yarshure On Thu, Jan 17, 2019 at 4:32 AM Howard Shere wrote: > > We can’t entirely stream from the files because we need to encrypt the > data. > > Any thoughts on using multiple threads rather than one? Or using the GPU > to

Re: I need some feedback

2019-01-16 Thread Howard Shere
We can’t entirely stream from the files because we need to encrypt the data. Any thoughts on using multiple threads rather than one? Or using the GPU to encrypt/decrypt the data? I lean towards using a single thread unless the performance becomes limited by the encryption/decryption work,

Re: I need some feedback

2019-01-10 Thread Quinn "The Eskimo!"
On 10 Jan 2019, at 15:42, Howard Shere wrote: > Lots of files. That’s likely to be the most interesting part of this. Transferring a single large file over Wi-Fi is pretty straightforward: Open a TCP connection and pour bytes down it. That’ll be fast and work well in a wide variety of

Re: I need some feedback

2019-01-10 Thread Howard Shere
Over wifi, but it needs to work over very busy wifi. On Jan 10, 2019, at 9:39 AM, Quinn The Eskimo! mailto:eski...@apple.com>> wrote: CAUTION: This email originated from outside of Synchronoss. On 10 Jan 2019, at 14:48, Howard Shere mailto:howard.sh...@synchronoss.com>> wrote: I am

Re: I need some feedback

2019-01-10 Thread Quinn "The Eskimo!"
On 10 Jan 2019, at 15:40, Howard Shere wrote: > Primarily images and videos. Just one file? Or lots of files? Share and Enjoy -- Quinn "The Eskimo!" Apple Developer Relations, Developer Technical Support, Core OS/Hardware

Re: I need some feedback

2019-01-10 Thread Howard Shere
Primarily images and videos. Multiple GBs of data. iOS 10 and later but older versions of iOS if it doesn’t add to the development... On Jan 10, 2019, at 9:38 AM, Quinn The Eskimo! mailto:eski...@apple.com>> wrote: CAUTION: This email originated from outside of Synchronoss. On 10 Jan

Re: I need some feedback

2019-01-10 Thread Quinn "The Eskimo!"
On 10 Jan 2019, at 14:48, Howard Shere wrote: > I am interested in finding the fastest possible way to transfer large amounts > of data between 2 iOS devices. Also, what does the connectivity look like? On the same Wi-Fi? Both on the Internet? Share and Enjoy -- Quinn "The Eskimo!"

Re: I need some feedback

2019-01-10 Thread Quinn "The Eskimo!"
On 10 Jan 2019, at 14:48, Howard Shere wrote: > amounts of data Define large? I’m not look for an exact number, just an expected order of magnitude. Also, what’s you minimum deployment target? Share and Enjoy -- Quinn "The Eskimo!" Apple