Suggested Improvement: Make Use of conversationID and id parameters, particulary wrt SMSThreads

[Joseph Malone]

If one wants to send an SMS attached to an older conversation rather
than potentially starting a new thread, one needs to use the
conversationID parameters. I am not sure the API handles that well
yet.

Here is an example:

an SMS to an existing conversation I have request payload:

id=477d2b310b8ecfb285111037aa3c631ddcf8cecf&phoneNumber=%2B16236525438&conversationId=477d2b310b8ecfb285111037aa3c631ddcf8cecf&text=doing%20a%20test&_rnr_se=YZPGUfDaxK%2Bz09IxQUHvS4ywMIg%3D

whilst what I think we do now - not starting a new conversation, the
request payload is:

id&phoneNumber=(510)%20984-2762%2C%20&text=4343434&sendErrorSms=0&_rnr_se=YZPGUfDaxK%2Bz09IxQUHvS4ywMIg%3D

If anyone wants to take this on, I am sure it would be very useful to someone!

By the way, I am not sure how I ever accomplished anything before
using the Google Chrome Development Tool.

[Joseph Malone]

I have implemented this change and updated the SVN and the Javadoc. I
will release a jar shortly.

[Rory]

Is the _rnr_se value required for sending SMS?

[Tobias Eisentrager]

I think it's required for all functions.

--
You received this message because you are subscribed to the Google Groups "Google Voice Java" group.
To post to this group, send email to google-v...@googlegroups.com.
To unsubscribe from this group, send email to google-voice-j...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-voice-java?hl=en.