Is it harmful to duplicate the post content in both
<div class="codo_posts_post_message">
and
<div class="codo_posts_post_imessage">

Why should Codoforum do that?

Hi,

It is for performance reasons.

One is an unformatted message that contains markdown or bbcode
and the other one is its HTML equivalent.

Hi @adesh ,

I knew it. But we only need it when editing the post. It rarely happens.
Why don't you query database to get the <div class="codo_posts_post_imessage"> when only user click on the edit button?

Hi,

Yes, we could do that, but we wanted the edit option to not have any lags due to slow response from server.

If we query from the database, the user will see a blank screen in the edit form for almost 1 second which we wanted to avoid.

But, after giving your reply a thought, we thought of this:

To edit a post, a user needs two clicks, that is first click the "three dots" at the top right of a post, then click on edit link.

So, what we can do is, on the first click, prefetch the post content from database.

What do you think about this ?

Well, it's nice. I posted many long posts into my forum and it's slow to display. Not sure if it hurts the SEO (duplicated content).

But I think its priority is low . Please process it when you have time.

I'm not sure this is a good solution.

Why waste space in the database for the same message twice?

This should done by HTML parser (or any other markup parser) in real time, without duplication of text.

This process can be done through Ajax almost immediately (without query database, similiar like live preview).

After all why use a markup language, when it can be added wysiwyg editor?
I personally was even more comfortable with BBCode than this markup language.

We save the message twice because it saves processing in the server side.

And if this processing is deferred to client side, then the pages will load slowly.

We wanted to avoid writing parsers for both server side and client side.

@castbound ,

I personally love markdown and don't like BBCODE .

@adesh ,

Currently, the page will load very fast when I editing post. But it will also load slowly when the fisrt time I load the page .

I'm realy like your solution!

To edit a post, a user needs two clicks, that is first click the "three dots" at the top right of a post, then click on edit link.
So, what we can do is, on the first click, prefetch the post content from database.

Query 2 fields with large post will not save anything In fact it will slow down page loading (client side - lot's of HTML code + Server side 2 fields with large text). Now imagine lot's of posts with lot's of text...

If you want to boost performance you should look at database structure. Missing lot's of indexes. Try to enable slow queries logs and queries without indexes to see what's going on with database This will really boost perfomance a lot and should be known to any developer.

@nguoianphu well, wysiwyg editor is even better.