Closed mariusnita closed 9 years ago
That's good!
I was also thinking about using the term "Incrementally-loaded data" when talking about the cache. Like, to reference that it's some incrementally growing snowball of data on the client. You just signal what data you're going to need, and it adds itself to the pile of available cache. This term also interacts with the concepts for "partially-loaded objects" and the "cache."
Reminds me of the ever-growing all-annihilating technological blob in Akira https://www.youtube.com/watch?v=GkAPQXX0AEY
Oh yeah. Maybe that's a better name for ActiveREST. (It's this ever-growing technological blob...)
No, I'm not suggesting we change the name to "Akira." That would be too obvious.
"Blob." ;)
Haha... It's like something that gets bigger and bigger, but it's Good. It's like the Force. Like the oxygen rushing into a room when you open the window. It's gaseous and God-like.
Maybe the bREAST is a big ever-growing blob of pleasure and heavenly sustenance.
Here's a view on the spirit of BREST:
fetch()
)save()
)BREST is both a library, and a RESTful design pattern that uses the library. But you can use the library without fully adopting the design pattern.
Wait, you're serious about calling this project BREST?
toomim wrote:
Here's a more ... sales-pitch view on the spirit of BREST:
- Insight: we can connect a React app to a REST-style API with very little code, and get for free: o one-way data binding with realtime updates (|fetch()|) o single call to change data on client and server (|save()|) o local cache of a subset of the REST database o partial data downloading o loading indicators when the current page needs more data o learning to pre-fetch the required data over time, before it's needed
— Reply to this email directly or view it on GitHub https://github.com/TheInvisibles/BREST/issues/6#issuecomment-45423377.
Yes, it's my current favorite name. I don't know any other libraries that reference breasts. I think ActiveREST is funny to me, but I don't think the joke is very accessible. I think BREST is more accessible.
It makes me uncomfortable. I imagine that I am not alone in that.
toomim wrote:
Yes, it's my current favorite name.
— Reply to this email directly or view it on GitHub https://github.com/TheInvisibles/BREST/issues/6#issuecomment-45423424.
When I wanted to name my old company friendbow, and have a big gay rainbow logo, that made people uncomfortable too. There's nothing wrong with breasts.
QED
I'm sorry for having invalid feelings.
toomim wrote:
When I wanted to name my old company friendbo, and have a big gay rainbow logo, that made people uncomfortable too.
— Reply to this email directly or view it on GitHub https://github.com/TheInvisibles/BREST/issues/6#issuecomment-45423486.
Haha. Well now that we have a flamboyant name and a disruptive coding style, time to get to work on some architecture.
Thanks.-o-o--o----o-------o------!-!!!
Maybe it's useful to step back and re-iterate the key points of ActiveRest. I see these:
setProps()
on the root with the new datasave()
on an object or byI kinda want to state the core points without mentioning with the details of implementation -- like whether you use url key/value pairs to denote object state, etc.