|
| |
| | "Archives" |
 | | Until now, hypermedia engines either provided a fixed hypermedia data model and left extensions to the hypermedia application or they left the modeling of the hypermedia data completely to the application developer and only provided storage functionality which had to be plugged into the data model by the application developer. | | | In the HyperStorM hypermedia engine, the storage layer and the application layer of a hypermedia systems are implemented within the object-oriented database management systems VODAK. | | | As an alternative, we propose an extensible object-oriented hypermedia engine which supports the specification of application semantics as application classes within the hypermedia engine, thereby supporting complex operations maintaining application-specific as well as application -independent constraints. |
|
http://www.cs.brown.edu/memex/archives.html
|
|
| |
| | WDVL: XML Resources |
| | As the first step, our plan is to develop a lightweight XML persistent storage engine on top of a relational database backend to come up with a UI and API in short time and replace it by our native XML storage system in the second step to satisfy complex XML processing requirements. | | | The XML media types Request for Comments 3023 (Jan. 2001) "standardizes five new media types -- text/xml, application/xml, text/xml-external-parsed-entity, application/xml- external-parsed-entity, and application/xml-dtd -- for use in exchanging network entities that are related to the Extensible Markup Language (XML). | | | The www.xmlrpc.com site supports the development of "simple cross-platform distributed computing, based on the standards of the Internet." XML-RPC (Remote Procedure Call) is "a spec and a set of implementations that allow software running on disparate operating systems, running in different environments to make procedure calls over the Internet. |
|
http://wdvl.com/Authoring/Languages/XML/Resources.html
(6409 words)
|
|
| |
| | WDVL: XML Resources |
| | As the first step, our plan is to develop a lightweight XML persistent storage engine on top of a relational database backend to come up with a UI and API in short time and replace it by our native XML storage system in the second step to satisfy complex XML processing requirements. | | | The XML media types Request for Comments 3023 (Jan. 2001) "standardizes five new media types -- text/xml, application/xml, text/xml-external-parsed-entity, application/xml- external-parsed-entity, and application/xml-dtd -- for use in exchanging network entities that are related to the Extensible Markup Language (XML). | | | two programs may internalize the same XML document into objects built from different classes." Quick is based on a schema language, QJML "to define markup languages and their relationship to Java classes. |
|
http://wdvl.com/Authoring/Languages/XML/Resources.html
(6409 words)
|
|
| |
| | Paul Thurrott's SuperSite for Windows: Windows "Longhorn" FAQ |
| | Originally expected to be a fairly minor upgrade, Windows Longhorn will now include a number of new features including a revised task-based (or "iterative") user interface, an extensible, dock-like, Sidebar, and a SQL Server 2003-based storage engine called WinFS (Windows Future Storage). | | | Remember that Windows XP was code-named Whistler and the next version of Windows, at the time, was code-named Blackcomb. | | | Windows "Longhorn" is the next major desktop Windows release, which will follow Windows XP; there is also a minor Windows Server revision that will ship in the Longhorn wave. |
|
http://www.winsupersite.com/faq/longhorn.asp
(6409 words)
|
|
| |
| | Hexapedia - Active Directory |
| | The AD database, the directory store, in Windows 2000 uses the Jet-based Extensible Storage Engine (ESE98), limited to 17 terabytes and 10 million objects in each domain (a theoretical limit, no more than 1 million is advised). | | | Certain objects also have a User principal name (UPN, from RFC 822), an objectname@domain name form. | | | AD internally uses the LDAP version of the X.500 naming structure. |
|
http://www.hexafind.com/encyclopedia/Active_Directory
(1287 words)
|
|
| |
| | Dwarf |
| | MIME parser: the parsing engine may be reimplemented for the top efficiency according to the currently used mail storage. | | | Dwarf Mail Server is targeted for both end users who are just looking for simple, secure and robust mail server as well as developers who need an extensible and powerful framework for application message processing. | | | The server implementation is based on the unparsed byte streams whenever possible, including its own and highly efficient MIME parser. |
|
http://www.gnome.sk/Dwarf/dwarf_mail.html
(548 words)
|
|
| |
| | Dwarf |
| | MIME parser: the parsing engine may be reimplemented for the top efficiency according to the currently used mail storage. | | | Dwarf Mail Server is targeted for both end users who are just looking for simple, secure and robust mail server as well as developers who need an extensible and powerful framework for application message processing. | | | Since the server is based on the Dwarf framework, it also shares its common design principles and features - simplicity, high modularity and extensibility, authentication and authorization, XML-based configuration, logging and remote management. |
|
http://www.gnome.sk/Dwarf/dwarf_mail.html
(548 words)
|
|
|
