0x5a177

One difference to note is that HTTY puts you in a REPL-like environment instead of being a one-shot command like curl.

Hi Mike, please, no need to apologize for the delay. I really appreciate you taking the time to look at this.

These are all great points, especially regarding the signup process and and permissions. I think you have validated some of the concerns that I have had regarding these issues.

I do have delete and rename, but maybe I should pop up a quick intro screen for first-time users to get acquainted with the functionality.

Thanks again and all the best to you.

Using Node has helped me think more in terms of streams because the APIs afford such thinking. PHP has streams but I never thought to use them, and I haven't really seen it done.

Node Streams really help performance in my application where I am proxying API calls from the browser to the Dropbox API. It's much faster to stream the response from Dropbox through to the client rather than request, wait for entire response, then send.

Learning Backbone is a great way to get practice with MVC and the "Observer" pattern if you haven't done it before.

Also it's a much better way of organizing your DOM structure than a bunch of loose jQuery calls.

I agree. I don't know about TCP behavior, but this seems really wrong in the sense that it ignores HTTP semantics of GET and POST. I imagine this could cause unintended effects in intermediaries like caching proxies.

I keep 2 plain text files:

1. backlog.txt - a list of all potential ideas and tasks

2. changelog.txt - a list of iterations/versions/milestones

Whenever I have an idea or bug, I add it as a line in backlog.txt When I want to actually work on code, I pick 3-4 tasks that I want to complete and move them to changelog.txt. The number of tasks depends on how much I can do in one or two sittings.

backlog.txt is in a format like this:

* Fix IE9 compatibility

* Refactor CSS

* ... etc

changelog.txt looks like this:

1.1.0 - next release

--------------------

* Fixed IE8 thingy

* SSL encryption enabled

1.0.9 - March 10, 2012

--------------------

* Fixed null-pointer crash

* Catch exception in sendmail.java

* Enabled websockets transport

Keeping everything in plain text helps me from fiddling around too much with the tool, which I am very prone to do. (Meta-bonus, my product is a text editor so I can organize my product with itself.)

Cool. I wanted to do something just like this, except the messages would decay over time.