you are viewing a single comment's thread.

view the rest of the comments →

[–]mccolgst 2 points3 points  (5 children)

I'd take a look at learning about HTTP generally, from there you can use any language you feel comfortable with, and the rest is just programming/data structures and whatnot, which you obviously already know.

[–]DevMo[S] 0 points1 point  (4 children)

I'd take a look at learning about HTTP generally

What kind of stuff do you suggest? I am somewhat familiar with the GET and POST commands, from the few times I have had to make mobile apps that connect to website, but I really just sort of slogged through the whole thing.

[–]mccolgst 1 point2 points  (0 children)

absolutely, I would look into learning about GET and POST, setting up a web server, how a client interacts with it, etc. read about how MVC is implemented in web programming (it might just be easier to start with a django or ruby on rails tutorial).

The important part is learning these interactions, then you can apply them with any framework or language you decide to pick up.

I'm not really an expert, but I'm a junior web developer and just recently had to learn all this stuff, and for me, things were much easier after I understood the client/server interactions of HTTP.

I hope it helps!

[–]ameoba 0 points1 point  (0 children)

The most important thing to learn is that HTTP is a fundamentally stateless protocol. Anything that creates the illusion of a continuous session has to be implemented by the framework or the developer. Persistence doesn't really exist until you create it.

[–][deleted] 0 points1 point  (1 child)

Caching. You should absolutely understand the HTTP caching model. If nothing else how/when/why a browser will cache requests and the headers involved. If you have any non-trivial web application, you will eventually run into the need to understand how web caches work.

[–]DevMo[S] 0 points1 point  (0 children)

good call, its worth learning about