wolf359 posted at 7:36AM Thu, 22 August 2019 - #4360097

But primarily because the Daz ,single workstation content management system is a NON starter for professional team environments no matter how good the content looks in the promo renders.

Slight OT: DS' CMS uses Postgres as its base DB, which can very easily be made multi-user/server-based, since, lacking only something similar to Oracle's RAC, psql is an enterprise-grade RDB. You can do this right now just by changing a few settings, but DAZ can write a few bits o' code to make it user-proof and UI-friendly if it ever becomes that big of a priority.

...and to be blatantly obvious about it (and include Poser users!), you don't really even need a database - Poser and DS users can both do this right now - they can simply chuck in read-only network file-shares as 'Runtimes', and let their local CMS DBs soak it in, which makes the whole distributed CMS thing kinda moot (besides, you really, really, really want to have users keep their CMS DBs local and the assets remote on NFS/CIFS drives - that way you can centralize the content/disk-usage but customize the UX in that department. Not like you're gonna swallow that many IOPS on assets after the initial file loads. With a bit of work by dev teams, you can even temp-cache those files on local disk with maybe a 7-day purge-after-non-use timer?)