Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

Not applicable

Ajax vs IE plugin

Hi,

What is the difference between using Ajax and IE Plugin? As per my knowledge, we need to install IE Plugin but what is the advantage of using it?

Thanks

1 Solution

Accepted Solutions
MVP
MVP

Re: Ajax vs IE plugin

Hello,

As far as the network configuration is concerned, there may be a big difference: AJAX always communicates to a Web Server (either QVWS or IIS). Plugin acepts qvp:// pseudo URLs, so the communication is done directly between the QVS and the Client. This method is considerably faster, but requires ports 4747 and 4774 opened in both client and server both inbound and outbound.

When port 4747 is not accesible by the Plugin client, the server falls back to HTTP tunneling (port 80). This will degrade performance, because security packets are transferred and the network traffic and the use of bandwidth increases. Communication in this case is always between Client and WebServer on one side and WebServer and Server on the other.

I'd say that the biggest advantage of AJAX client is that it doesn't require any installation on the client's side, but it may require some design tuning.

It's up to you to choose one option or the other, avoiding tunneling when possible. In short, Plugin requires software installation client side, but rendering is WYSIWYG. AJAX doesn't need any installation other than a browser, but it may lack some design options.

Hope that helps.

8 Replies
rahulgupta
Contributor III

Ajax vs IE plugin

Hey hi,

More of the Solution to your query can be solved in the discussion done in the below link......

http://community.qlik.com/forums/t/33896.aspx#136911

Hope this works...!!

MVP
MVP

Re: Ajax vs IE plugin

Hello,

As far as the network configuration is concerned, there may be a big difference: AJAX always communicates to a Web Server (either QVWS or IIS). Plugin acepts qvp:// pseudo URLs, so the communication is done directly between the QVS and the Client. This method is considerably faster, but requires ports 4747 and 4774 opened in both client and server both inbound and outbound.

When port 4747 is not accesible by the Plugin client, the server falls back to HTTP tunneling (port 80). This will degrade performance, because security packets are transferred and the network traffic and the use of bandwidth increases. Communication in this case is always between Client and WebServer on one side and WebServer and Server on the other.

I'd say that the biggest advantage of AJAX client is that it doesn't require any installation on the client's side, but it may require some design tuning.

It's up to you to choose one option or the other, avoiding tunneling when possible. In short, Plugin requires software installation client side, but rendering is WYSIWYG. AJAX doesn't need any installation other than a browser, but it may lack some design options.

Hope that helps.

Not applicable

Ajax vs IE plugin

That's really helpful Smiley Wink

dvqlikview
Honored Contributor II

Ajax vs IE plugin

Miguel - This is very useful! Thank you very much Smiley Happy

Cheers!

Not applicable

Ajax vs IE plugin

Myself, I prefer IE plugin .. because of the WYSIWYG

dvqlikview
Honored Contributor II

Ajax vs IE plugin

Totally agreed. Even we use IE plugin and explain the same to end user. But only draw back is that we need to stick to IE and can't use other browsers Smiley Sad

Cheers!

Not applicable

Ajax vs IE plugin

you are right! nothing is perfect Smiley Sad and nowadays lots of ppl start using safari, firefox.. sigh Smiley Sad

then the best solution is AJAX Smiley Sad happy redesign then~ olala

Not applicable

Ajax vs IE plugin

hi miquel,

"requires ports 4747 and 4774 opened in both client and server both inbound and outbound."

can you tell me how to open port 4747 and 4774 in server?

thanks before.

Regards,

Heri