Dean Oo wrote:but am having a hard time passing the information via AJAX since a web page is pretty large and the querystring can only have so much information.
Bear Bibeault wrote:
Dean Oo wrote:but am having a hard time passing the information via AJAX since a web page is pretty large and the querystring can only have so much information.
Then don't pass it in the query string.
Paul Clapham wrote:First step would be to determine the requirements.
It doesn't make sense to say you want to "get the HTML into text", because HTML is already text. And there's this "hidden markup"... what is that?
And when your client is viewing a web page, what are they using to do that? A browser connected to the web page? A text editor looking at the source code... the HTML?
And are these web pages just anything they can get to on the web, or just the web pages served by your site?
Eric Pascarello wrote:"content was too big" What is too big?
Have you gone through basic Ajax tutorials on how to send post data to the server and dispay a result on the page? If you have not, it might be a good time to try it and not jump right into a big task.
Eric
Eric Pascarello wrote:Why are you converting it to a textfile?
I would request the page that you are grabbing the contents for and output back the response to the client. No need to store it in a txt file unless you play on using that at some later time and do not want to fetch it again.
Eric
Eric Pascarello wrote:If you are going to request the file via Ajax it is not going to be a textfile in the responseText.
Eric
Eric Pascarello wrote:Offtopic..Can I ask why you type your response before the quoted text. It is rather backward convention.
Eric
Dean O'olish wrote:Easier to read
Bear Bibeault wrote:
Dean O'olish wrote:Easier to read
For who? Certainly not the typical reader of these forums.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?