![]() |
devNote
d071002 |
|
{tbd}
{tbd}
{tbd}
{author note: This folio is started with boilerplate that is not appropriate for this topic. It will be cleaned up later.}
- 2007-10-26-10:10 64-bit Feasibility
- Envisioning of ODMA64 presumes that certain desirable qualities of ODMA integration remain important and feasible. We don't know what the answer will be to that, but the architectural structure we explore is the appropriate one for migration from an engulfed ODMA32 (identified informally as the ODMA 2.5 framework).
As part of technical risk management for ODMA64, this should reveal where mitigation needs to be explored and confirmed before going to far in anticipating a successful ODMA65 effort.
- 2007-10-26-09:52 64-bit Ignorance
- I know nothing about the 64-bit platforms and what happens with the x64 versions of Windows with regard to 32-bit interoperability, what the boundaries are, and what the differences in 64-bit development are over 32-bit development.
I am going to assume that access to 64-bit arrangements from 32-bit applications will be as constrained as the case was from 16-bit to 32-bit. I don't know what the game will be for accessing 32-bit processes from 64-bit ones, and especially how GUI integration might happen in that case. I am assuming there is a story and that it is not that hard to figure out when I finally dig deeper.
I am also assuming that the idea of achieving a kind of ODMA 2.5 for migration around ODMA32 can work, and that this is enough for a leap into ODMA64 and some sort of ODMA 3.0 specification that does not carry any of the deprecated elements of ODMA 2.5.
-- Dennis. E. Hamilton
- Hamilton, Dennis E.
- ODMA64 3.0 Interoperability -- Opportunities and Constraints. AIIM ODMA Interoperability Exchange, ODMdev Development Note page d071002c 0.01, February 15, 2008. Available at <http://ODMA.info/dev/devNotes/2007/10/d071002c.htm>.
![]() |
created 2007-10-25-19:20 -0700 (pdt) by
orcmid |