datasheet,schematic,electronic components, service manual,repairs,tv,monitor,service menu,pcb design
Schematics 4 Free
Service manuals, schematics, documentation, programs, electronics, hobby ....


registersend pass
Bulgarian - schematics repairs service manuals SearchBrowseUploadWanted

Now downloading free:xerox 19771107 Adding New Devices To The Channel Interface

xerox 19771107 Adding New Devices To The Channel Interface free download

Various electronics service manuals

File information:
File name:19771107_Adding_New_Devices_To_The_Channel_Interface.pdf
[preview 19771107 Adding New Devices To The Channel Interface]
Size:202 kB
Extension:pdf
Mfg:xerox
Model:19771107 Adding New Devices To The Channel Interface 🔎
Original:19771107 Adding New Devices To The Channel Interface 🔎
Descr: xerox sdd memos_1977 19771107_Adding_New_Devices_To_The_Channel_Interface.pdf
Group:Electronics > Other
Uploaded:04-03-2020
User:Anonymous
Multipart:No multipart

Information about the files in archive:
Decompress result:OK
Extracted files:1
File name 19771107_Adding_New_Devices_To_The_Channel_Interface.pdf

Inter-Office Memorandum DRAFT - DRAFT - DRAFT - DRAFT To Pilot interest Date Novem ber 7, 1977 From Paul McJones Location Palo Alto Subject Adding new devices to the Channel interface Organization SO~/SO XEROX XEROX SDD ARCR1VES _ I have .roaCt and undo1"::;tood. Filed on: [lfs]Channel.memo rag es __,_.---'fo - , - - - - - 'f'I _ _ __ 1h~e Reviewer_----- # of Pages _ __ Ed. -t1SDQ-.:2 feJ4 The problem The Channel interface in the second draft of the Pilot Functional Specification has the property that adding a new device requires editing and recompiling the Channel DEFINITIONS module, and thus all the modules which include it. This is in conflict with the desire not to recompile the system except for the semiannual releases (assuming new devices are to be added between releases). Thus we propose a revised Channel interface, which, it is claimed, solves the recompilation problem. The problem with the current interface stems from its dependence on the enumerated type Channel.DeviceType, which has a value for each implementation of the interface. Adding a new implementation requires adding a new value to DeviceType, and also adding corresponding variants to the definitions of the DeviceType-tagged variant record types DeviceSelection, PhysicalRecordStatus, DeviceCommand. DeviceStatus, and "Rep" (the private record to which a Handle points). (It is worth noting that these variant records constitute a nuisance for both client and implementor. Most values crossing the interface must be wrapped in a variant record constructor, and then "unwrapped" with a one-armed WITH statement essentially doing at runtime what Mesa is meant to do at compile time.) A solution Half of the operations in the current interface do not depend on DeviceType. and so are not a problem: Delete Suspend Restart GetPhysicalRecord PutPhysicalRecord Those which do depend on DeviceType are: Create (accepts DeviceSelection) WaitPhysicalRecord (retu rns PhysicalRecordStatus) Comm

>> View document online <<



>> Download document << eServiceInfo Context Help



Was this file useful ? Share Your thoughts with the other users.

User ratings and reviews for this file:

DateUserRatingComment

Average rating for this file: 0.00 ( from 0 votes)


Similar Service Manuals :
xerox 01a INTRO - xerox 01b BKPLN - xerox 03 MEAT - xerox 04 DIM - xerox 05b KBD - xerox 06 CRAM2K - xerox 06 CRAM3K -
 FB -  Links -  Info / Contacts -  Forum -   Last SM download : Samsung VP-W70,71,75

script execution: 0.02 s