Changes between Initial Version and Version 1 of Ticket #1334, comment 7


Ignore:
Timestamp:
Jul 20, 2014 8:46:41 AM (5 years ago)
Author:
ExtraBattery
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1334, comment 7

    initial v1  
    55In my tests (on I2P 0.9.13-0.) I passed a base64 destination to SAM v1 and it said "SESSION STATUS RESULT=OK DESTINATION=...", repeating the destination I passed. Maybe it had an internal error that it didn't reveal at that point and that's why my further operations (sending and receiving a datagram) failed.
    66
    7 Can you confirm that it is possible to pass a 516 char long base64 destination to SAM v1 in the "SESSION CREATE STYLE=RAW ..." message and get a "RESULT=OK" back? Judging from the documentation it's an error. Maybe it's already fixed in the recent 0.9.13-x dev build, maybe not.
     7Can you confirm that it is possible to pass a 516 char long base64 destination to SAM v1 in the "SESSION CREATE STYLE=RAW ..." message and get a "RESULT=OK" back?
    88
    99About comment 5: I assume SAM v3 ignored the ID parameter for "DATAGRAM" sessions all along and just used a random ID instead. It would be great to have this fixed too. In 0.9.16...