|
|
| (3 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | {{glossary}}
| + | #redirect [[Services]] |
| − | {{stub}}
| |
| − | == Printing On Demand ==
| |
| − | *[[W:Espresso Book Machine]] ''- print books on demand - general concept''
| |
| − | *[http://www.lightningsource.com Lightning Source]
| |
| − | **[http://www.lightningsource.com/links.aspx#AuthorServicesLinks List of on-demand printing businesses]
| |
| − | *[http://www.ondemandbooks.com/home.htm On Demand Books (ODB)]
| |
| − | *[http://www.lulu.com/ Lulu]
| |
| − | | |
| − | == Production On Demand (POD) ==
| |
| − | *[[W:POD]]
| |
| − | *[http://www.zazzle.com Zazzle] ''- on-demand printing of merchandise''
| |
| − | *[http://www.cafepress.com/ CafePress] ''- on-demand printed merchandise and CD/DVD's''
| |
| − | *[http://finerworks.com/pricing.asp finerworks.com] and [http://www.canvasondemand.com/canvas-sizes.asp CanvasOnDemand] ''- printing/framing/mounting photos on canvas''
| |
| − | | |
| − | == On Demand in Software Architecture ==
| |
| − | This concept of production on demand also plays an important role in software architecture and programming environments. Complex applications like office suites and content management systems can have huge arrays of diverse components and modules. Applying the on-demand paradigm in this context simply means to only load those components into memory when their first required.
| |
| − | | |
| − | This issue is closely related to the programming environment as well, for example the so-called "stateless" paradigm which is the client-server/request-response system used on the web is not a very on-demand environment. This is because every request has to run its own instance of the server application. Although shared-object architectures can help with this, it would be supported from the ground up in a peer-to-peer architecture.
| |
| − | | |
| − | == See also ==
| |
| − | *[[Open Source#Open Source hardware|Open Source hardware]]
| |
