jshttp / jshttp.github.io Goto Github PK

like https://github.com/visionmedia/node-ratelimiter

send data allows you to send information down the response.

The send-data module has 8 different functions for 8 different content types and does not try to guess what the correct encoding is.

It also has logic to handle gzip encoding.

i think i wanna see how this plays into the router and such. preferrably the router would use it

would anyone be offended if i moved the stuff in makefile into the npm scripts?

The following session modules are kind of cool:

• generic-session
• redsess and level-session

The latter two are implementations of generic-session.

• npm downloads

What else?

https://github.com/expressjs/resolve-path

i use it, but i think it needs a second look. i'm not sure what send, serve-static, and family does right now. assigning to @dougwilson to decide :)

like busboy and multiparty

Would be cool if these modules and any related ones have a common error syntax. Would be cool to have err.code matching node or something as well as .status if applicable

okay so i realized that i need on-finished for read streams as well i.e. incoming client responses. it has to be on-end.

This project sounds like a documentation site for a set of low level modules to work with http servers in node.

I've done similar things with ( https://github.com/Raynos/http-framework/ ) and I think philosophies are very likely to align.

I'd be willing to move any modules that make sense from ( https://github.com/Raynos/http-framework/tree/master/modules ) into the jshttp organization.

If you find any modules in http-framework that are a good fit, I'd happily move them into jshttp & contribute and maintain them there. If there are modules in http-framework that are too "high level" / "opinionated" / "out of scope" then they will just stay under my name and have nothing to do with jshttp.

None of the modules that are part of http-framework are in any way branded with it.

I did a similar collaboration with npm-dom ( https://github.com/npm-dom ) a while ago where I moved low level modules to work with the browser DOM from my name into the npm-dom organization and left high level or opinionated modules under my own name.

I suspect that express / koa / http-framework can all use modules from the jshttp organization.

cc @jonathanong @dougwilson

can we create a new session module can be used in all web frameworks?

• cookie session
• generic session

body is a thin layer on top of raw-body

It exposes the ability to fetch a form encoded body or json encoded body or to inspect the content-type header and parse the body according to the content type.

we need to put up somewhere a "who are we?" paragraph. explaining who is running jshttp, etc.

Okay just realized the layout doesn't make sense. Each module needs a description on how it is important. I'll mess with it later unless someone else gets to it first

i would put this in the same boat as accepts

send data allows you to send information down the response.

The send-data module has 8 different functions for 8 different content types and does not try to guess what the correct encoding is.

It also has logic to handle gzip encoding.

@jshttp/owners

What should the website convey? Right now I've heard talk about adding more badges, but maybe it'd be good to think about what purpose the site should serve. From my needs I'd expect it to have at least the following information per project:

• Project name
• Project description (!)
• NPM version
• Node compat version
• Link to NPM
• Link to GitHub
• Link to possible documentation page

What am I missing from the list?

gotta ask that dude

for etag header parsing/comparison; not sure if it'll have generation or that will be a different module

Although the name is jshttp, I see this org more for anything that satisfies "tools to BYO server-side js web framework". Some definition and a vote would be nice.

needs keygrip to be finished and moved to crypto-utils. then v1!

if anyone wants to speed this up, do a code review please :) i've been waiting on one forever...

i'll probably work on this later

since the version badges are not an official service (perhaps someone might get shields.io to add it, ehh?), i thought i would put down the different ones with there colors here:

with 0.8 or lower being bright green, 0.10 being green and 0.11 being orange for not the greatest support, haha. the numbers would all go up one with 0.12 comes out, so 0.10 would then be green, etc.

locking issues is like the best feature in github. we should always lock an issue/pr when we close it and think the user is satisfied and doesn't need to respond. this prevents people from randomly posting in some old issue about an unrelated problem.

...or whatever. i don't want to put gittip badge in the readmes any longer :)

base-line compression for http messages (framework-agnostic)

would be cool if we made this page standard and had other orgs use the same template. then we could have them all crosslinked.

for ex, we might want to link the following orgs in this org:

• expressjs
• koajs
• pillarjs
• crypto-utils for keygrip
• stream-utils for all the request stuff

tho maybe the -utils orgs could use better names

@dougwilson @Fishrock123 did one of you guys get a domain already? want to setup google analytics for all our team pages? main thing is that i don't like how it's commented out. haha

o.O

or whatever it's called to basically wrap raw-body with HTTP stuff

i'd like a better name...

thoughts on where to add the jshttp logo (and website link) in the module readmes

move it here. make it part of the jshttp.github.io page.

would be pretty cool

• mime-types
• compressible
• set-type

etc. we'll create mime-db first, then we can decide here how to create the APIs. mime-types and compressible APIs could probably stay the same.

i have https://github.com/koajs/spdy-push. just need to make it generic once node supports http2

Would be nice if the org linked to the site in the description.

https://github.com/aaronblohowiak/routes.js

Routes is a really minimal router inspired by express.

I think it was literally broken out of express 3 years ago.

just wanted to post here that i grabbed the twitter handles jshttp and pillarjs. i'm not sure what we'd use them for, but at least we won't end up like expressjs :D

issue for all of TJ's stuff. i'll ask him whether he'd like to move them in or whether we should just fork it after we decide. add/remove to the list:

• https://github.com/visionmedia/node-basic-auth
• https://github.com/visionmedia/node-fresh
• https://github.com/visionmedia/node-methods
• https://github.com/visionmedia/node-range-parser
• https://github.com/visionmedia/send - maybe not because @dougwilson wants to split it up anyways

https://github.com/component/path-to-regexp/issues/8

we can move it once:

• duo is released and supports redirects
• we get blake onboard

routes-router is a module on top of routes.

It's a http specific request handler that does routing for you.

It includes a prefix feature to nest routers recursively.

I strongly suspect this modules is too opinionated / high level but i'll leave this issue open.