Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ipfs web apps architecture(s) #51

Open
dryajov opened this issue Apr 18, 2017 · 3 comments
Open

Ipfs web apps architecture(s) #51

dryajov opened this issue Apr 18, 2017 · 3 comments
Labels
status/ready Ready to be worked

Comments

@dryajov
Copy link
Member

dryajov commented Apr 18, 2017

I think we've got a great list of things collected here from the standpoint of the end user interaction as well as browsers vendors. What I haven't seen being captured in one single place, which IMHO is part of this effort, are the possible web application architecture(s), patters and guidelines and what is currently possible with IPFS in the browser from the stand point of building an app. I know this might feel unrelated to the current effort, but IMHO it is.

I see two points worth capturing and expanding:

  • How would you build an IPFS enabled web app currently?
    • What can you serve from IPFS and what has to be served over good'ol HTTP
    • ...
  • What would be the ideal support required from the browser and ipfs itself to build the next gen web apps?
    • This is heavily discussed in this repo, but not consolidated under an issue that someone evaluating the technology can use to gain a clear understanding of what this offers him/her as an app developer/vendor.

How is this relevant to browser vendors?

  • Its relevant to know which primitives the browser already offers and how they can be used with IPFS, their possibilities and limitations - i.e. ServiceWorkers, etc...
  • We need to be able to say what are the ideal IPFS primitives required and what the next gen apps would look like (pretty ambitious, but worth thinking about in this context)
  • The above will also allow understanding better what would be the transition path web app developers would need to follow to get from whats currently possible without native support to what will be possible once native support is there.

If this sounds like something worth discussing, I suggest we get on a call to further discuss it and capture the outcome here later on.

@flyingzumwalt @lgierth @diasdavid @kyledrake @kumavis @Gozala @haadcode

(apologies if this has been already discussed elsewhere - I couldn't find anything in specific in this repo)

@dryajov
Copy link
Member Author

dryajov commented Apr 19, 2017

Linking @kumavis solution #52.

@daviddias daviddias added the status/ready Ready to be worked label Dec 13, 2017
@Kamelia2000
Copy link

hello possible to make realtime application like IM messenger based on IPFS ?

@lidel
Copy link
Member

lidel commented Feb 24, 2018

@Kamelia2000 yes, pubsub experiment was added last year:

If you want to go in-depth, check additional pubsub resources suggested by @victorbjelkholm:

Everything pubsub in one comment!
How it got started: ipfs/notes#64 (2015)
Notes on simple initial implementation (floodsub): https://github.com/libp2p/pubsub-notes
The future of pubsub in IPFS: https://github.com/libp2p/research-pubsub
Check out both the notes and issues in the two last repos, as there is information there as well.
Some more links to further information is here as well: ipfs/js-ipfs#580

IPFS community is building realtime apps with it, quite successfully so far:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/ready Ready to be worked
Projects
None yet
Development

No branches or pull requests

4 participants