Flexible Data I/O
Varied inputs
Likewise, the inputs may entail more than those conducted by the in-house editorial staff. Content infomediaries, wire services, content partnerships and other subscriptions mandate an API for getting editorial in to the content management system. Perhaps specific components are best delivered by protocols/languages that the user's client is aware of.
  • Web forms
  • Applet text-editors
  • WebDAV
  • XML uploads
The possibilities are many, so design for accomadating them all.
Slide 11 of 37 Contents
  1 |   2 |   3 |   4 |   5 |   6 |   7 |   8 |   9 | 10
11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20
21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30
31 | 32 | 33 | 34 | 35 | 36 | 37
www.arachna.com > Educational Resources > Conference Presentations
spidaman
 		© 2000-2008 Ian Kallen | Copyright Notice