wiki:PyWacket/Capabilities

Capabilities

Needed technical capabilities, standards

Implementation environment, computer language in a general sense, not software products.

A lot of this stuff following is 'gleam-in-the-eye' type of technology, that is, nice to have some time on the future ... what do I actually need now ? Maybe three or four of the following.

Environment

Basically, these 'environmental arenas':

  1. Desktop ( GUI )
  2. Server ( public or private network )
  3. Console ( non-GUI )
  4. Mobile or Info Pad ? ( like tablet or netbook )
  5. Cloud ( such as Google )

Platform

... working in these 'technical arenas':

  1. Linux
  2. Windows
  3. Macintosh
  4. Android ( if possible )

Time for a Matrix ?

Linux Flavors Microsoft Windows Apple Android Other OSs
Desktop ( GUI ) Notes/Linux#Desktop Notes/MicrosoftWindows OSX, via ? ?
Console ( non-GUI ) Notes/Linux#Console readline console, but no curses ? x
Server ( private network ) Notes/Linux#PrivateServers XAMPP, Twisted, Python servers Linux x
Server ( public network ) Notes/Linux#PublicServers X X X X
Mobile Notes/Linux#Mobile Windows 10 iOS No real Python, Java only
Cloud ( Google, Amazon ) Notes/Linux#Cloud Azure ? ?

Technical Capabilities

Following list is very overlapping and redundant.

Permanent Servers

  • Service discovery
  • Standard ports

Intermittent Services

  • Connect-Disconnect
  • Bind on demand

Peer2Peer Servers

  • Messaging
  • Synchronizing

Integration Architecture and Standards

  • usual suspects, next item
  • Formats, for example creole wiki markup
  • Maybe process/workflow language
  • Database standards, if any. Self-made standard like SQLAlchemy

Standard Servers and Protocols

  • HTTP
  • SSH
  • XMPP
  • AMQP
  • SMTP
  • FTP
  • Samba

Ad Hoc Servers

  • Messaging backplates
  • Multiprocessing pipelines

Network Management

  • Global Naming, DNS
  • Service Discovery
  • Monitoring, particularly security.

Application Frameworks

  • Mostly python
  • How big is it ?

UI Frameworks

  • Graphical versus non-graphical
  • event/process monitor
  • ad hoc data entry
  • mostly python ( pref pyGTK / Glade )
  • HTML5 and WebSockets ?
  • smaller, better

Command Interpreters

  • Little cmd type apps
  • Python console apps
  • Localhost telnet apps
  • Extended IRC

Integrated Process Launcher & Monitoring

  • Pythonic base for bash and Linux commands ?

Integrated Process Platform

  • Start/bind on demand
  • Process patterns
  • Process templates

Database And Persistence

  • RDF relation Idiom
  • integration over multiple machines/users
  • Extract / merge databases
  • Synchronize
  • Database conversion, version-to-version, SQLite to MySQL etc.
  • MongoDB and SQLite

Messaging

  • combined with ftp, console commands
  • Message queue, process pipelining
  • Real messaging like Jabber etc.

Email servers/clients

  • Ad-hoc info sharing
  • Public vs. Private

Info Drop Boxes

  • Web Sockets
  • Repository ( preferably Bazaar )
  • MongoDB

Desktop Integration

  • XML-RPC possible on private network, not on public
  • X Forwarding
  • Messaging ( how ti use public services ? )
  • Apps that have built in synch capability, maybe Zim Wiki
  • email via Twisted SMTP

Desktop-Server Integration

  • Start-Stop services, start-on-demand, monitoring
  • Note that XML-RPC on a public network is not on unless tunnelled or intermittent
  • Public server is read-only, Admin server is locahost with tunnelling ?

User Management

  • Each client mach/os is user on server ( ex. hc-pclos, cq-ku, cq-w7 )
  • "PyWacket" presence discovery on public and private networks

Public Presence Management

  • All those little public presences: google, twitter, facebook, vendor, financial, etc. etc. accounts

Also See

Last modified 2 years ago Last modified on 06/23/2015 12:41:33 PM