How many characters can go in a string I store via newUpdatePersonAppDataRequest?

I'm not sure of the total, but I wouldnt reccomend using it at this point, as it's functionality is brittle. I think this question has been asked before, but I don't think it was answered.

 I was going to try to come off flippant with the response "as many as you want as long as you don't care if you read them back or not", but I realized that wouldn't be very constructive .  That part of the API doesn't seem to work and if you take a look at this link: http://developer.myspace.com/community/myspace/opensocial.aspx at the very bottom of the page in the section titled "Stuff that isn't Implemented", you'll see that App Data is something that isn't implemented yet.  Unfortunately you'll have to "roll your own" for now untill they wire up that part of the API.  I've already got a working SOA pattern so if you want to collaborate drop me a line.

$cott:

you'll see that App Data is something that isn't implemented yet

Some if the docs here are quite out of date.

App data is "working" - not sure the limit but suggest [as with most things round here] you trial and error it to find how much can be stored.

Eddie

 Well, I beg to differ, but App Data is not working.  I've got an Orkut application that uses the App Data API and it works fine in the Orkut sandbox.  I take that code and move it over to MySpace without modification and it stops working.  I've also copied and pasted the example (please see the other thread associated with saving app data for a discussion on that example) and it doesn't work either.  The fact that known good code fails on MySpace leads me to believe that MySpace has the issue and not my code.  That, coupled with the fact that the examples that MySpace provides on their site for interacting with App Data don't work, lead me to believe this still hasn't been implemented.  I've asked in the thread before and I'll ask now, if someone from MySpace can chime in on this as to the status of the App Data API I think that it could really clear up some confusion.  Until then my web service that talks to a MySQL database to store key/value pairs works like a champ.

Hey $cott,

I did put 'working' in quotes...as this is myspace and things are not always quite as they appear...

But here's one of my apps that uses app data to save colors and speed... OK it's Flash and uses REST api to store the data which is probably not how you are doing it...

www.myspace.com/randomfriendviewer

Click on the color circle top right on canvas to set app data stored on myspace.

Eddie

 Hey Eddie,

   So true about the "working" part - lol - as I'm becomming painfully aware.  I went ahead and created a data store though and wired up some services for registration and unregistration (when user adds or removes the application).  I've also got some services wired up to save data keyed by applicationId which is a guid that I provide in the registration/unregistration url.  If I used the oauth_consumer_key it would require me to create the application in MySpace before I can create the corresponding record in the database, a pattern I'm not keen on. 

I'm using flex to provide the UI so I'll probably look into the REST API a bit later.  I've still got a learning curve with flex, although with ActionScript it almost feels like old school java applet programming.