A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.
2 added 44 characters in body
source | link

For #1: For .Net MVC based implementations, the Jar files are needed if you want to enable in context editing for your website (which uses Tridion APIs), else you do not need the Jars as part of your actual website. For oData service(from Tridion) setup you will need these jars. Responsibility of oData is to serve content to the consumers (in this case the website). and the website does not need the jars

For # 2: The distribution of content is done via the deployer module and you do not need the JARs on your consumer. The deployer will deploy content to the appropriate target based on the settings in the configuration files. HTTPUpload and deployer module are the same

For #3: It depends upon what is your deployment architecture. If you use oData and have this setting for cache as "true" on oData, then deployer will communicate with oData using cache channel service to clear cache on publish. And consumers who call oData will get the latest content on every publish (provided there is no local caching on consumer side which is the actual website).

For #1: For .Net MVC based implementations, the Jar files are needed if you want to enable in context editing for your website (which uses Tridion APIs), else you do not need the Jars as part of your actual website. For oData (from Tridion) setup you will need these jars. Responsibility of oData is to serve content to the consumers (in this case the website).

For # 2: The distribution of content is done via the deployer module and you do not need the JARs on your consumer. The deployer will deploy content to the appropriate target based on the settings in the configuration files. HTTPUpload and deployer module are the same

For #3: It depends upon what is your deployment architecture. If you use oData and have this setting for cache as "true" on oData, then deployer will communicate with oData using cache channel service to clear cache on publish. And consumers who call oData will get the latest content on every publish (provided there is no local caching on consumer side which is the actual website).

For #1: For .Net MVC based implementations, the Jar files are needed if you want to enable in context editing for your website (which uses Tridion APIs), else you do not need the Jars as part of your actual website. For oData service(from Tridion) setup you will need these jars. Responsibility of oData is to serve content to the consumers (in this case the website) and the website does not need the jars

For # 2: The distribution of content is done via the deployer module and you do not need the JARs on your consumer. The deployer will deploy content to the appropriate target based on the settings in the configuration files. HTTPUpload and deployer module are the same

For #3: It depends upon what is your deployment architecture. If you use oData and have this setting for cache as "true" on oData, then deployer will communicate with oData using cache channel service to clear cache on publish. And consumers who call oData will get the latest content on every publish (provided there is no local caching on consumer side which is the actual website).

1
source | link

For #1: For .Net MVC based implementations, the Jar files are needed if you want to enable in context editing for your website (which uses Tridion APIs), else you do not need the Jars as part of your actual website. For oData (from Tridion) setup you will need these jars. Responsibility of oData is to serve content to the consumers (in this case the website).

For # 2: The distribution of content is done via the deployer module and you do not need the JARs on your consumer. The deployer will deploy content to the appropriate target based on the settings in the configuration files. HTTPUpload and deployer module are the same

For #3: It depends upon what is your deployment architecture. If you use oData and have this setting for cache as "true" on oData, then deployer will communicate with oData using cache channel service to clear cache on publish. And consumers who call oData will get the latest content on every publish (provided there is no local caching on consumer side which is the actual website).