Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Multi-function printer
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Software development kits== In addition to specific software packages, many vendors also provide the ability for the user to develop software to communicate with the MFP through a [[Software development kit]]. Different vendors have different licensing models, from completely "closed" proprietary systems (often with large costs involved) to open strategies with no direct cost involved. An incomplete list of these technologies is: * [[OmniPage|Nuance OmniPage]] * [[Canon MEAP]] (Multifunctional Embedded Application Platform) * [[HP Open Extensibility Platform (OXP)]] * [[Konica Minolta OpenAPI]] * [[Lexmark Embedded Solutions Framework (eSF)]] * [[Ricohโs Device SDK]] * Samsung XOA - eXtensible [[Open Architecture]] * [[Sharp OSA]] (Open Systems Architecture) * [[Toshiba OPA]] (Open Platform Architecture) * [[Xerox EIP]] (Extensible Interface Platform) In general, these technologies fall into one of two technical models - Server based, or MFP internal software. Server based technologies use a method to communicate information to and from the MFP (often [[SOAP]]/[[XML]] based), running the operating code on a suitably powered computer on the network. This method has the advantage of being very flexible, in that the software is free to do anything that the developer can make the computer do. The only limit from the MFP itself is the capability of the MFP to display a user interface to the workings of the application. As many of the applications are based around custom printing, scanning and authentication requirements, the MFP manufacturers that use this method gravitate towards these core technologies in the user interface. MFP internal software, by comparison, has the advantage of not requiring anything outside of the MFP. The software runs within the MFP itself and so even a complete network outage will not disrupt the software from working (unless of course the software requires a network connection for other reasons). MFP internal software is often, but not always, [[Java (programming language)|Java]] based and runs in a [[Java virtual machine]] within the MFP. The negative side to this kind of software is usually that it is much more limited in capabilities than Server based systems.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)