The To Do list for ESAWEB

This list is sorted by the current priority. If you think the priority should change, please let Barton know.

  1. PL1 Interface(24) This is needed to support some high level applications including some graphics functions, who knows.
  2. Open Edition:( ) Open edition needs to be installed for testing of Apache.
  3. Byte File System:( ) Because we think we're better than UNIX, we should support their file system so they can port their applications to ESAWEB. This support is necessary to enable much of the potential applicatons that could be ported to VM.
  4. WebGateway Function Replacement:( ) CICS/VSE interface.
  5. Proxy Support:( ) This would be cool!!! (Found on the www listserv.) Another option for SSL support is to front-end your VM Web server with a unix box running Netscape Proxy server. The proxy server is configured as a 'reverse proxy server'. Clients on the Internet connect to the unix box. The unix box passes non-SSL requests through to the VM web server. The connection from the unix box to the client is SSL. From the unix box to VM is standard HTTP. The certificate and SSL overhead is all on the unix box which is acting as a gateway and SSL encrypt/decrypt machine. This isn't a perfect solution, but it does give you basic SSL support. We've been doing this for more than a year.
  6. Header Support/Mime Multipart:( ) CICS/VSE interface.
  7. Java servlet Support:( ) (Sun's Specification http://java.sun.com/products/servlet/index.html ). It would be nice to convince IBM to port Websphere Application Server to VM.
  8. GUI web browser editor:( ) Because it would be a fine application.
  9. Hidden Paths:(8 ) Some SFS directory paths should remain hidden.
  10. Image Maps:( ) To be competitive, image maps should be supported.
  11. PUT Support:( ) This is to allow users to PUT data to a file on the server dyanamically.
  12. Apache Install and Benchmarks:( ) Lets find out how good we really are.
  13. HTTP 1.1:( ) Persistent connection is already supported, but there's some other stuff:
    - byte range to serve PDFs one page at a time.
    - status codes
    - request codes
    - caching
  14. OV Mail Support:( ) Why bother?
  15. OV Calander Support:( ) Why bother?
  16. BFS Support for REXX, Perl, C and Shell:( )
  17. Examples:( )
    - Applets demonstrating performance graphs, charts
  18. Developer Package:( )
    - Connect to any DB on VM
    - Connect to DB2 MVS
    - Execute a CICS Transaction
    - Run a CGI on another platform and return results via a java application
    - Ship Perl, NetRexx and Java with install documentation

A little help from our friends

If you would like to help, the following work needs to be done and won't interrupt any work already ongoing:

  1. O/E installation at VSI
  2. Byte file system installation DONE!!!
  3. Image map function, callable
  4. Apach Installation
  5. graphics functions
  6. Porting of O/E stuff
  7. Developer package stuff
  8. OV Interfaces
  9. BENCHMARKS:

If you can't measure it, I'm just NOT interested!(TM)

COPYRIGHT 8, 1996 - VELOCITY SOFTWARE, INC. WEBMASTER@velocity-software.com