Design PhilosophyOLI~ h~ndarnental design pliilosopli!, I-equired usingtlic Internet and its infr'istr~~ctu~.c as buildi~ig blocksti)r OLI~ collaboration softusare. After yars of esperimcntingand collaborating to develop an opcnprocess, the Internet developers realized that theIntcrnct had reached a state ofcritical niass. In the caseof ncnvorks and connccti\ity, reaching critical mass isa tremendous i~npet~~s for ngrccing on ,I commonsta~~ciard. As more and Inorc users acccss the Internet,tllc need for soh\.are dc\~clopmc~lt for the I~lternctalso increases. In addition, the \,cr!, nature of tlicInternet demands an opcn standardization process toensure the long-term \.iability of a product.Our philosophy also included the reuse of existingolx~i software as building blocks \\,licne\~er possiblc.In addition to our choice of building upon theI~itcrnct and thc WWW tcclinolog!,, \\.e selectedthe 'rool Co~n~nand La~ig~~agc (TcJ) as the primarylangu;~ge for cie\.eloping most of o111 application anciuser interface f~inctions.~ We also took 'id\.antagc ofthe database library in thc Rcrltclcy UNIS distributionfor built-in databasc support.'Another objective \\,as to mnltc sure our so%\.arc\vould be easy to port to all the rclc\,ant operatingsystem platfol-ms. This principle guided our selcctiollofcomponcnts and lhclpcd us isolate 3 small set ofplatforni-ciependentf~~nctions illto a special library forporting the soh\lare.As stated earlier, \\.c tried to take an object-orientedapproach \vhenevcr possible. The ad\.anta~es of ourapproach became incrcasingl!. apparent as more peoplebecame involved \vitli the sofnvarc development.The object-oriented approach made component reusefcasi blc.FrameworkOur fi-a~nc\~~orlt orga~lizcs the AltaVista Forum soft-\\!arc into n1.o layers: toolkit and ~lpplications. The toolsrcquircd to build the applications overlap each other.kVc hnve used them to build generic npplications,including a discussion application tliat supports iucrsdiscussing a set of related topics, nlucli like ne\\.sgroupsdo; a calend'lr applicatio~i that supports users' abilitiesto sclicdule elrents o ~i a specific date ,~nd,~ta particulartime; and a nc\\.spapcr npplicntion tl~~t provides a person~lizcdnci\.s filtering scr\.icc. \Vc envision that, o\.crti~nc, the fr.~me\\rork \ire Iia\~c dc\,clopcd \\rill supportn 11i111ibcr of divcrsc applications. Figure 1 sho\vs theAltaVista Forum toolkit and application la!lcrs.Tlic toollit is a combination of both C and Tcl codethat creates the follo\ving intcrhcc components:Ruilt-in databasc. The applic~ition ~ ~scs a built-ind.ir.ib,~sc to storc its object instances. The databascis \.c~-!~ simple rclatioli,iI moiicl \.irith an objecthict-arch!, relationship t;~cilit\r a\railable to those.~pplic.~tions rliat need it. The librrir\r also pro\,idcsinversions on ccrtai~i attributes to support fastrctl-ic\d and sorting based on attribute values.l
Grc~pliical objccts such as definitions of b~~ttons,toolbars, various objccts that arc part of a form(c.g., select boses, radio buttons, checlc boses, textboscs), and icons.l>,~t.ibnsc entries, tlie definitions of their attrib~~tcs,anti default \,ali~es.User interfke aggrcgatc objects such as for~iis,\,icws, dialogs, and error messages.I)cfiii~lt access control policies, including debultgroups, acccss riglits, and their mappings, to control\\rho call access indi\.idual fi)ru~ns and \\,hatactions tlic!l can take \\.ithin them.This approach encapsulates thc dct'~ils in lo\\,-lc\rclmociulcs, malu~ig tlie soft\\rarc more readable andmaintainable. It also makes it cas!, for different functionsto reuse the objects.To f~~rtlicr hcilitate code sIi,lring, the framc\\~orl
- Page 1:
IINTERNET PROTOCOL V.6DigitalTechni
- Page 6 and 7:
lie! elements of the protocol,Digit
- Page 8 and 9:
Intcrnct. Within tlic IETt', severa
- Page 10 and 11:
~~scd to store Iicccssar!z ciata an
- Page 12 and 13:
packets, \\,hilt the latter avoids
- Page 14 and 15:
* Test address for IPv4 characteris
- Page 16 and 17:
ROUTER SOLICITATIONTYPECODECHECKSUF
- Page 18 and 19:
7 .ncn\.orlt. The solution is to al
- Page 20 and 21: AUTOCONFIGURATIONPROCESSINGUSER SPA
- Page 22 and 23: pilssing tlic olx~i x)ckcts to them
- Page 24 and 25: James P. BoundJIII~ Bol~nd 15 ,I co
- Page 26 and 27: process of restoring a p;~rtic~~I~r
- Page 28 and 29: Table 2 (continued)Year Item Descri
- Page 30 and 31: Table 3Goals of the Australian Digi
- Page 32 and 33: fidelity, tlic tcst of \\~liicli is
- Page 34 and 35: An important consideration is that
- Page 36 and 37: Table 8Architectures Implemented by
- Page 38 and 39: ucoder~ novaNOVA simulator V2.2bsim
- Page 40 and 41: BiographiesMaxwell M. BurnetMax Bur
- Page 42 and 43: no\\. tli;it appropriate stantlards
- Page 44: High Perfor~nance Fortran V1.l is c
- Page 47 and 48: 5. For ca;i~i~l~lc scc /'I.OC.CY'L/
- Page 49 and 50: tllc s\,stcIn under test to use the
- Page 51 and 52: WAREHOUSEW.89,0.000089'WDISTRICTW'1
- Page 53 and 54: III 8-CPU. 8-GB 8-CPU, 8-GB II -II
- Page 55 and 56: ~ILI~LIC. In othcr \\.orcis, the gr
- Page 57 and 58: ~norc to ~ I ~ S L Ithe I . ~ ~.cj>
- Page 59 and 60: 13. 1)igital Eqi~ip~ncnt Corporatio
- Page 61 and 62: TPC-C Benchmark7 -.I. lie TPC-C bcn
- Page 63 and 64: Lock OptimizationL,ocl
- Page 65 and 66: DATABASE CACHE SIZE IN GBFigure 2Ua
- Page 67 and 68: Engineering Group); Marl< Davis and
- Page 69: H\,pcrtc\-t Transfer I'rotocol (HTT
- Page 73 and 74: select box part of the toollcit pro
- Page 75 and 76: work on it was limited, \ve divided
- Page 77 and 78: Further ReadingsThc Digital Technic
- Page 79 and 80: J. Iroccssor," PI-ocec~di7rg.i ?/'l
- Page 81 and 82: B. Lce, E. Atnkov, and J. ClementM.
- Page 83: Printcd in U.S.A. EC-N7285-18/9612
Change language