default search action
Google
Google Scholar
Semantic Scholar
Internet Archive Scholar
CiteSeerX
ORCIDJames E. White
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2010 – 2019
- 2012
[c6]James E. White, Jean H. Chang, N. Catherine Hogan, Ian W. Hunter:
Development of a lorentz-force actuated intravitreal jet injector. EMBC 2012: 984-987
2000 – 2009
- 2001
- [j5]Dan Kalman, James E. White:
Polynomial Equations and Circulant Matrices. Am. Math. Mon. 108(9): 821-840 (2001)
1980 – 1989
- 1989
- [j4]James E. White:
ASN.1 and ROS: the impact of X.400 on OSI. IEEE J. Sel. Areas Commun. 7(7): 1060-1072 (1989) - 1983
- [j3]David D. Redell, James E. White:
Interconnecting Electronic Mail Systems. Computer 16(9): 55-63 (1983) - [c5]Franklin Kuo, Debra Deutsch, Harry C. Forsdick, J. J. Garcia-Luna-Aceves, Najah Naffah, Andrew A. Poggio, Jonathan B. Postel, James E. White:
Panel on multimedia computer mail - technical issues and future standards. SIGCOMM 1983: 191-196
1970 – 1979
- 1977
- [j2]James E. White:
Elements of a Distributed Programming System. Comput. Lang. 2(4): 117-134 (1977) - 1976
- [c4]James E. White:
A high-level framework for network-based resource sharing. AFIPS National Computer Conference 1976: 561-570 - [c3]James E. White:
A Network-Wide Virtual Programming Environment. Berkeley Workshop 1976: 119- - [c2]James E. White:
Distortion in disc recording systems. ICASSP 1976: 541 - [i29]James E. White:
Elements of a Distributed Programming System. RFC 708: 1-30 (1976) - 1975
- [i28]James E. White:
High-level framework for network-based resource sharing. RFC 707: 1-29 (1975) - 1974
- [i27]Mark Krilanovich, George Gregg, Wayne Hathaway, James E. White:
Comments on the File Transfer Protocol. RFC 624: 1-3 (1974) - [i26]Jon Postel, James E. White:
Procedure call documents: Version 2. RFC 674: 1-6 (1974) - 1973
- [i25]James E. White:
Use of FTP by the NIC Journal. RFC 479: 1-5 (1973) - [i24]James E. White:
Host-dependent FTP parameters. RFC 480: 1 (1973) - [i23]James E. White:
Request for network mailbox addresses. RFC 510: 1-2 (1973) - [i22]James E. White:
Proposed Mail Protocol. RFC 524: 1-40 (1973) - [i21]James E. White:
Responses to critiques of the proposed mail protocol. RFC 555: 1-11 (1973) - [i20]Abhay K. Bhushan, Kenneth T. Pogran, Raymond S. Tomlinson, James E. White:
Standardizing Network Mail Headers. RFC 561: 1-3 (1973) - 1972
- [j1]Vinton G. Cerf, Eric Harslem, John F. Heafner, Robert M. Metcalfe, James E. White:
An Experimental Service for Adaptable Data Reconfiguration. IEEE Trans. Commun. 20(3): 557-564 (1972) - [i19]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, Bob Sundberg, Dick Watson, James E. White:
The Data Transfer Protocol. RFC 264: 1-9 (1972) - [i18]James E. White:
Tenex interface to UCSB's Simple-Minded File System. RFC 409: 1-8 (1972) - 1971
- [c1]Robert H. Anderson, Eric Harslem, John F. Heafner, Vinton G. Cerf, James Madden, Robert Metcalfe, Arie Shoshani, James E. White, David C. M. Wood:
The Data Reconfiguration Service - an experiment in adaptable, process/process communication. Symposium on Problems in the Optimizations of Data Communications Systems 1971: 1-9 - [i17]James E. White:
Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB. RFC 105: 1-9 (1971) - [i16]Robert D. Bressler, Stephen D. Crocker, William R. Crowther, Gary R. Grossman, Raymond S. Tomlinson, James E. White:
Output of the Host-Host Protocol Glitch Cleaning Committee. RFC 107: 1-12 (1971) - [i15]Eric Harslem, John F. Heafner, James E. White:
Network activity report: UCSB Rand. RFC 113: 1-2 (1971) - [i14]James E. White:
Network specifications for UCSB's Simple-Minded File System. RFC 122: 1-21 (1971) - [i13]James E. White:
Typographical Error in RFC 107. RFC 132: 1 (1971) - [i12]Robert H. Anderson, Vinton G. Cerf, Eric Harslem, John F. Heafner, James Madden, Robert M. Metcalfe, Arie Shoshani, James E. White, David C. M. Wood:
Status report on proposed Data Reconfiguration Service. RFC 138: 1-23 (1971) - [i11]Robert H. Anderson, Vinton G. Cerf, Eric Harslem, John F. Heafner, James Madden, Robert M. Metcalfe, Arie Shoshani, James E. White, David C. M. Wood:
Data Reconfiguration Service: An implementation specification. RFC 166: 1-20 (1971) - [i10]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Bob Sundberg, Dick Watson, James E. White:
The Data Transfer Protocol. RFC 171: 1-9 (1971) - [i9]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Bob Sundberg, Dick Watson, James E. White:
The File Transfer Protocol. RFC 172: 1-12 (1971) - [i8]Vinton G. Cerf, Eric Harslem, John F. Heafner, Bob Metcalfe, James E. White:
The Data Reconfiguration Service - Compiler/Interpreter Implementation Notes. RFC 194: 1-18 (1971) - [i7]James E. White:
A User TELNET Description of an Initial Implementation. RFC 206: 1-14 (1971) - [i6]James E. White:
Telnet Access to UCSB's On-Line System. RFC 216: 1-16 (1971) - [i5]James E. White:
Specifications changes for OLS, RJE/RJOR, and SMFS. RFC 217: 1-2 (1971) - [i4]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Bob Sundberg, Dick Watson, James E. White:
The File Transfer Protocol. RFC 265: 1-12 (1971) - [i3]Abhay K. Bhushan, Robert T. Braden, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Robert L. Sundberg, Richard W. Watson, James E. White:
Revision of the Mail Box Protocol. RFC 278: 1-4 (1971) - 1970
- [i2]James E. White:
Specifications for Network Use of the UCSB On-Line System. RFC 74: 1-9 (1970) - [i1]Eric Harslem, John F. Heafner, James E. White:
NCP Status Report: UCSB/Rand. RFC 78: 1 (1970)
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from 
to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the 
of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from 
, 
, and 
to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from 
.
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-04-25 05:52 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint
dblp was originally created in 1993 at:
since 2018, dblp has been operated and maintained by:
the dblp computer science bibliography is funded and supported by:
