02-12-2012, 05:13 PM
Nasir Wrote:I built a proof of concept for this a long time ago if you're interested in talking about where I went with it. My biggest tip is DO NOT use an external database. There's no need for that and all you'll run into is syncing issues when there are server crashes and what not. Just set up a json endpoint within the RunUO server and communicate that way.
Exactly. The data is already available (in memory) so there's no need to also store it in a database that would require a db hit anytime someone hits the page (if some type of caching strategy isn't used). Not taking into account sync issues due to server crashes, but just the fact that whenever items are bought/placed/removed/modified you would need to update the database to reflect this or have a cron task that runs to do it (and then potentially having stale data).
Set up a service within the server that exposes the data in json and have some javascript on the client that pulls it and formats it into some searchable grid/list/table to view. It doesn't have to be pretty, just functional. I think displaying items and allowing searching would be a great first goal.