Ok.
In that case then the easiest solution I can think of is to do
something similar to Facebook where session keys. Right now I use the
session generated from the fb connect api to pass to the Server side
java libraries.
On Apr 28, 12:26 pm, Taylor Singletary taylorsinglet...@twitter.com
On Apr 28, 12:06 am, MJ lor...@gmail.com wrote:
Also I am using @anywhere to login but I also have some server side
code with java. Is there a way that I can pass the credentials of the
@anywhere logged in user to the server side code? Or does that happen
automatically (once someone
Don't mean the credentials (password) but if a user authorizes my app
to for example post tweets to their account via @anywhere will my
server side libraries (using JTwitter) have the same permissions
provided that they are using the same API Key and Secret Key?
On Apr 28, 4:06 am, glenn gillen
Hi MJ,
The access tokens used transparently behind the scenes in @Anywhere aren't
compatible with the OAuth 1.0A access tokens Twitter uses in the standard
API implementation. We're looking at creative ways to bridge the gap but
won't have an easy solution for this for a bit.
Taylor Singletary
