Redvant: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 19: Line 19:
and "vant" is just from haskell-servant.
and "vant" is just from haskell-servant.
</div>
</div>
<div style="background-color: #fbfcf8; color: black;">
<div style="font-weight: normal;background-color: #fbfcf8; color: black;">
= Substance =
= Substance =
<br><span class=plainlinks>
<br><span class=plainlinks>

Revision as of 10:33, 20 January 2024


Purpose

The primary purpose of the Redvant moniker is to name the separation of some product lines from their domain space aspects. Products developed under its rubric can be compiled for operation strictly on the basis of the FOSS or COTS software upon which they are based without any integration with DS though in some cases this can gut the app if presentation of a DS feature was its purpose. A non-DS application can then supply a new purpose. My tl;dr line and other apps sold on stores may thus have core function repurposed to such new apps without committing to DS ops.

However this separation is only in evidence at the time of it's application in such non DS development activity. Redvant exposition is largely or entirely in terms of its use in domain space and does not further comment on this separability .

Précis

Redvant , or '<dcms' (dcms-bra), is a collective term for software including react and servant within a DCP context and packaged as a reusable resource demonstrated in various applications such as the tl:dr and by the KEE.


"red" could be

react, redis, light in the ~700 nm range, a proper name as in red5, the parfume, riding hood, Malcom X, Simply, etc..

and "vant" is just from haskell-servant.

Substance


Use of Apache ISIS or other fat DDD pkg is intended later in our overall DDD product line engineering (as 'redvantis'). Some enterprise users may prefer the java basing of ISIS or an ERP core and this is anticipated for later development.

Visibility

This is the sole exposition at this scope and will remain so. Technical detail will be in an eponymous § in the Books DCMS volume.