[OTR-dev] anything else for the libotr 2.0.0 API?

[Adam Fritzler]

In the ALWAYS case, what happens if there's more than one attempt to
send a message before negotiation completes?  It looks like it's
silently lost, which there should at least be a warning about.

asf.


On Fri, Jan 28, 2005 at 02:25:04PM -0500, Ian Goldberg wrote:
> You can see the libotr CVS snapshot in the usual place:
> 
> http://www.cypherpunks.ca/otr/libotr-cvs-latest.tar.gz
> 
> Here's the ChangeLog so far (since 1.0.4).  The new callbacks aren't
> tested yet, since that will require changes to gaim-otr.  :-)
> 
> So: do people have more requests for the libotr 2.0.0 API?
> 
>    - Ian
> 
> 	* src/message.h: New callback for fetching OTR policy
> 	* src/message.c (otrl_message_sending): Create a ConnContext if
> 	we don't have one already.  Use it to fetch the OTR policy.
> 	Just return if the policy is NEVER.  Only append the whitespace
> 	tag if the policy is OPPORTUNISTIC or ALWAYS.  Don't send
> 	unencrypted messages in ALWAYS, but store them for
> 	retransmission later.
> 	* src/message.c (otrl_message_receiving): Fetch the OTR policy.
> 	Just return if the policy is NEVER.  Only send a Key Exchange
> 	Message in response to an unexpected Data or Error Message in
> 	OPPORTUNISTIC and ALWAYS.  Only recognize the whitespace tag in
> 	OPPORTUNISTIC and ALWAYS.