D17841: Workaround for bluetooth payload transfer bugs

[Matthijs Tijink]

mtijink added a comment.


  In D17841#383743 <https://phabricator.kde.org/D17841#383743>, @sarcot wrote:
  
  > Just so you know, I initially had the payload transfer going over the existing bluetooth connection (by sending the payload transfer info followed by the payload itself), but if the payload had newline characters, then the processing got messed up (because newlines got stripped off as part of regular message processing). Also, with payloads of unknown lengths, it wouldn't be easily possible to determine the end of the payload. Therefore, I split it out to a separate connection.
  
  
  Makes sense. Sending it directly also causes problems for long transfers (e.g. file shares), so separating them makes sense. I'm trying to make something work in all cases.

REPOSITORY
  R225 KDE Connect - Android application

REVISION DETAIL
  https://phabricator.kde.org/D17841

To: mtijink, #kde_connect
Cc: sarcot, kdeconnect, mschroeder, varunp, shivanshukantprasad, skymoore, brute4s99, wistak, anoopv, dvalencia, rmenezes, julioc, Leptopoda, timothyc, Danial0_0, johnq, Pitel, adeen-s, SemperPeritus, daniel.z.tg, jeanv, seebauer, bugzy, MayeulC, menasshock, mikesomov, tctara, apol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20181230/ef051de9/attachment.html>