Nutomic/ensichat

Ability to send files

Opened this issue · 10 comments

The ability to send files through the mesh would be awesome. And maybe even (sign the files, I think though that signatures are already in the protocol for text messages in EnsiChat if I am correct.

This is a bit complicated, as we'll have to split the files in chunks. And we need a better routing protocol, as flood routing will probably kill all connections when a lot of data is transferred.

That's true. There are obviously more efficient routing protocols, I do not know what they r called, but I think one of them is dynamic routing. Anyway, I agree that the routing protocol should later be updated.

Is this because antennas connect to devices one by one and sweep through them by connecting and disconnecting to the devices.

Sent from my iPod

On Jul 23, 2015, at 1:21 AM, Felix Ableitner notifications@github.com wrote:

This is a bit complicated, as we'll have to split the files in chunks. And we need a better routing protocol, as flood routing will probably kill all connections when a lot of data is transferred.


Reply to this email directly or view it on GitHub.

No, it's because messages are sent to every connected device, on the entire network. Bluetooth has concurrent connections afaik. So it's just a problem of the app code.

Oh okay.

Sent from my iPod

On Jul 24, 2015, at 12:54 AM, Felix Ableitner notifications@github.com wrote:

No, it's because messages are sent to every connected device, on the entire network. Bluetooth has concurrent connections afaik. So it's just a problem of the app code.


Reply to this email directly or view it on GitHub.

I was wondering, Canada Bluetooth device send data to a device right at the exact same time as another? Physically that really doesn't sound right?

Sent from my iPod

On Jul 24, 2015, at 12:54 AM, Felix Ableitner notifications@github.com wrote:

No, it's because messages are sent to every connected device, on the entire network. Bluetooth has concurrent connections afaik. So it's just a problem of the app code.


Reply to this email directly or view it on GitHub.

I don't know how this is on a physical level, but it should work with the Android API.

Yeah. Okay. Just saying the physically realm. Nothing happens at once, there is always the first command. Parallel processing does not exist if the commands to do the processing cannot be executed at the exactly the same time.

Sent from my iPod

On Jul 24, 2015, at 3:26 PM, Felix Ableitner notifications@github.com wrote:

I don't know how this is on a physical level, but it should work with the Android API.


Reply to this email directly or view it on GitHub.

That's nothing I'm really concerned with :p

Yeah. Just saying my thoughts. But as long as the android api acts like so then it works.

Sent from my iPod

On Jul 24, 2015, at 7:41 PM, Felix Ableitner notifications@github.com wrote:

That's nothing I'm really concerned with :p


Reply to this email directly or view it on GitHub.