Since we have OTRDATA working in ChatSecure, I'm taking this opportunity to think about what the OTRDATA API should look like in otr4j. I would like to make it as simple and as standardized as possible so that it will be easy to add to apps.
I think I finally have a grasp on the whole OTRDATA stack. Right now, a lot of the OTRDATA API in ChatSecure is in the ChatSecure code. ChatSecure's otr4j is just providing the very lowest level of support, providing ChatSecure with the raw TLVs. I think this API should not expose TLVs at all. I'm currently thinking otr4j should provide a dead simple interface for sending/receiving files. Since it is structured like HTTP GET/PUT, perhaps we should model Apache's HTTP Client API, and have classes for GET and PUT. .hc -- PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81 https://pgp.mit.edu/pks/lookup?op=vindex&search=0x9F0FE587374BBE81 _______________________________________________ Guardian-dev mailing list Post: [email protected] List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To Unsubscribe Send email to: [email protected] Or visit: https://lists.mayfirst.org/mailman/options/guardian-dev/archive%40mail-archive.com You are subscribed as: [email protected]
