Issue's with API

Hi guys,

I am messing around with the api to see if i can load my most recent files into my site for display and link back to flashden. I tried using version1 api and then noticed the the xml output would juggle positions. This also seem to be the case for edge as well. One minute the file title is in the first node then the next minute it’s in the last node. I would expect the xml would keep to one format of output?

Maybe it’s the way i am loading this into flash? Is there an example fla that shows the way it should be done?

is there an issue with the api?

I’m not sure if what you are experiencing is an issue with your code or the API , but yes, there are some issues with the API . The main one (for me anyway) is that it doesn’t fetch item thumbnails correctly.

All the data dopes seem to be correct, even the thumbnails(not before) Here is my output http://marketplace.envato.com/api/edge/new-files-from-user:Paul_Ferrie,flashden.xml

if you load the page up and after a couple of minutes refresh the page you will see that the items in the output change positions.

I’m not sure if what you are experiencing is an issue with your code or the API , but yes, there are some issues with the API . The main one (for me anyway) is that it doesn’t fetch item thumbnails correctly.

+1

This is being looked at now

The thumbnails are fine now.

One minute the file title is in the first node then the next minute it’s in the last node. I would expect the xml would keep to one format of output?

That’s a dangerous thing to expect, not even in regards to our API , but for XML parsing in general. There’s nothing in the XML spec that specifies that elements should be ordered. To quote this good article on xml design

For example, if you manage data in hash tables or other unordered data structures in the application domain, you might face additional work re-assembling elements into the order set by a schema. In records-oriented XML , you should probably use unordered patterns unless you have specific reason for ordering them (for example, when a specific order is already specified in the application domain model).

I don’t know much about how flash parses XML so you might need some help from some of the other authors on what the best practices are.

The thumbnails are fine now.

Can you also look at the bug where total_earnings = balance…

Not sure how possible but it would be sweet to split earnings into commission and referals… could you do that?

Cheers, keep up the good work

One minute the file title is in the first node then the next minute it’s in the last node. I would expect the xml would keep to one format of output?

That’s a dangerous thing to expect, not even in regards to our API , but for XML parsing in general. There’s nothing in the XML spec that specifies that elements should be ordered. To quote this good article on xml design

Maybe an extra parameter that allowed us to sort by name / date added etc.. or a node of the date the file was added so we can sort them chronologically…?