Rhonda,

Probably you mentioned my post when saying you not believe so. I will try to clarify what I are my assumptions.

1) It is impossible to create any interesting applications without some kind of storage. At least for user prefereces.

2) Currently there is no way to store data without calling external servers and storing data there.

3) MySpace will not allow to store data with external calls, since

a) there is risk that data will be used against mySpace TOS 

b) it is insecure, since with Javascript, users can change application created data before storing them with external calls.

Am I wrong with these assumptions?

Thanks,

Jevs. 

Hi,

Those are a lot of questions, and I honestly don't want to answer wrong.  Let me bring this to the attention of the developers, and see what I can find out.

Thanks for your patience :)

Rhonda

Sorry Jevs, my response was to the poster who asked if the generic storage was available yet.  I answered, that I didn't believe so.

Sorry for the confusion, but I will try to get some attention to these storage questions.. since this thread seems to be growing longer and longer ;)

Rhonda 

Jevgenijs:

Rhonda,

Probably you mentioned my post when saying you not believe so. I will try to clarify what I are my assumptions.

1) It is impossible to create any interesting applications without some kind of storage. At least for user prefereces.

2) Currently there is no way to store data without calling external servers and storing data there.

3) MySpace will not allow to store data with external calls, since

a) there is risk that data will be used against mySpace TOS 

b) it is insecure, since with Javascript, users can change application created data before storing them with external calls.

Am I wrong with these assumptions?

Thanks,

Jevs. 

  

 I'm not ronda, and I'm not a developer, but I'll try to answer... :)

1 - Yes. That is why we are creating a data api. You are also welcome to store any application specific data on your own server, and may cache user data for 24 hrs. 

2 - Yup. We will have a data api ready before launch.

3 - Don't follow?

4 - We are reviewing all applications on the site, including a code review (javascript included). People are gonna do nastiness, but we're gonna catch 'em.

Stephanie (Bam Bam),

Thanks for replaying,

Here are my comments:

2) Great, would be nice to have more information, for example which functions and which OS version is planned to be implented

3) I mean for example if  some OS application is storing profile data (say for all friends) and another application (not OS, not registred with MySpace) using them to publish outside MySpace. How you can contol it?

4) I mean by using Firebug anybody can change javascript while using it (not when it encoded and verified my MySpace)  and then let application to store malicious data, how you can prevent it if allowing external calls?.

Cheers,

Jevs.  

 I wub pennywise!!! :) hehehe

Just found excellent blog post on situation with Myspace http://thoughtlabs.com/cs/blogs/cappy/archive/2008/02/08/facebook-vs-myspace-opensocial-development.aspx , from which it follows that

If correct, my question are 

a) are there some working examples to ensure viewer id is passed securely to external servers?

b) what will be MySpace limitations on usage of this mechanism? I guees it will not be allowed to store the list of viewer ot owner friends. 

Thanks for any kind of info.

Jevs

I see that a launch date of March 13th has been announced for MDP, but I haven't heard anything about the availability of a data storage solution even though data storage is supposed to be available before launch. Any updates on this front?

Paul:

The storage API will be ready to develop against shortly and will be ready for primetime before launch of the application gallery to the public.

Good question.  I'll see if Paul has any updates on this.

Rhonda

This is something of a make or break issue for any number of reasons...

 This is someting of...  (that is the forum echo)

hehehe

I agree, with the echo, this is a make or break issue.  The data store needs to be ready now for us to work on, considering the launch date is now immediate.  I've been holding off this whole time on a rewrite of my code, considering its already working on other containers and it was promised that the data store would be there by launch.  This is starting to get close enough, that if the data store is not going to be ready within the next couple of days, I'd like an official response so I can switch my code over to do remote calls from my own server. The fuzzy words of "soon" don't help much, I don't mind if its far off, but if we have a date, at least i know how to plan.

Thanks.