Hacker News new | past | comments | ask | show | jobs | submit login

I mentioned multipart/x-mixed-replace above and I think it can work here instead of CSS. You never reload the chat history page, just put that in an iframe and use a separate iframe with a form that submits your newest reply.

Edit: actually this should work even without mixed replace.




When the form submits its frame refreshes ("navigates").


Right but reloading a static html asset (the reply iframe consisting of just a textbox) is basically free. So long as you separate the chat history window and the reply textbox/form into two separate frames, I don’t see the problem.


Using JavaScript is also “basically free”.

There’s no problem with either listed approach, GP just seems to consider a method without page reloads as adhering to a harder constraint.


Using JS would have broken the threat model of the dark web chatroom. So it is a non starter in that context.


I thought chrome killed x-mixed-replace (except for jpg images)





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: