Skip to content

Plugins issues #2

Description

@formula1
  • HTTP
    • Tends to act as a protocol that facilitates more complicated protocols
    • No expectations cannot exist until response occurs
    • Examples of standardization attempts within http umbrella
      • Serve Tars based on filepath
      • Serve Chunks/Torrent Compatible
      • Redirects
      • Acts as a facilitator to more complex communication (i.e git)
    • I may be forced to consider 'Requests' as their own object
  • IPFS - https://ipfs.io/, https://github.com/ipfs/js-ipfs-api
    • There is no native node server
  • Git
    • Git urls in the wild are usually based off https or ssh. This makes them difficult to handle
    • Git doesn't have its own protocol that is widely used.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions