Skip to content

(Valkyrie) Interfacing

RePod edited this page Feb 25, 2018 · 3 revisions

PSDLE utilizes Valkyrie proper to ensure high accuracy and less headaches for everyone involved. In doing so, the path to results is underwhelming compared to the old write ups!


Entitlements / Purchase History

"Generating the List: Valkyrie Edition".

PSDLE fetches an account's entitlements through the Macross Brain service.
That's about it, nothing fancy.

In earlier versions of Valkyrie, Macross Brain fetched Entitlements stored temporarily to be written to localStorage (for caching). If localStorage could not fit the contents (failed write), the expected content was blank when read back from localStorage thus no Entitlements would be available to the application. This has since been fixed, but temporary fixes at the time included manually increasing localStorage's capacity or in PSDLE's case reading from the temporary store before the failed write (this is currently still done).

Download Queue

PSDLE reads from and writes to the Download Queue through the Kamaji/Downloads service.

The previous Chihiro implementation was fairly accurate, though!

There's currently an issue with God of War HD collection (PS3/Vita cross-buy) in that the Vita version cannot by queued by PSDLE nor the original download list. Attempts to "enhance" around this problem (via queuing the item ID and SKU ID (PS3) to Vita) with PSDLE have also failed. Similar items may be affected.

Catalog

PSDLE fetches Catalog responses with the Susuwatari service.

Difficult to gauge accuracy with the old Chihiro implemenation, but mostly the same.

Miscellaneous

PSDLE utilizes the provided i18n (internationalization) service to format file sizes and dates in the locale (no regards to PSDLE language), and in the future possibly more.

utils/const is read for Kamaji-related values, like platform IDs and translating numbers to something human-readable.