¿Se pueden crear dinamáticamente los objetos de la gráfica abierta de Facebook?

Question

Estoy desarrollando una aplicación de Facebook.Tengo un objeto personalizado creado en el gráfico abierto, a continuación se enumeran son pocas de mis inquietudes

1. ¿Cada tipo de objetos en un tipo de objeto específico requiere una página web única?
2. Estoy usando JS SDK para publicar acciones de gráficos abiertas, ¿existe alguna regla de que la URL del objeto ("MyOBJECTROL" en el siguiente código) utilizo en la función JS para, por ejemplo:

   fb.api ('/ me / MyApp: MyAction' + '? MyObject= MyObjecturl & Access_Token= MyAccessToken', 'correo', {Scrape: True},

            function (response) {
                var msg = 'Error occured';
                if (!response || response.error) {
                    if (response.error) {
                        msg += "\n\nType: " + response.error.type + "\n\nMessage: " + response.error.message;
                    } alert(msg);
                } else {
                    alert('Post was successful! Action ID: ' + response.id);
                }
            });
   

   debería ser igual con el OG: URL en el metatag en el objeto?

   1. ¿Podemos pasar cualquier cadena de consulta junto con la URL de objeto que se puede recuperar en la página del objeto?

   2. ¿Cómo podemos publicar el mismo tipo de objeto con diferentes propiedades de objeto (por ejemplo, por ejemplo, diferentes URL, etc.)

      Cualquier ayuda es muy apreciada.

Answer 1

The answer is yes. Every instance of an object maps to a page, be it html, C#, php... whatever. So if you are a jquery ajax dynamic programmer you will have to shift your architecture or go without open graph.

My company http://www.fuhshnizzle.com uses jquery, ajax, Amazon S3 to create video playlists that run in the player. This is an extremely lightweight architecture. Recently we allocated resources to publish playlists directly to the open graph. Our senior architects did not initially grasp that this was not dynamic. They assumed they could define the objects like C# classes for example, and then instantiate them dynamically at publish time.

There was quite a bit of consternation that in our case we would have to publish one web page per playlist and then the issue came up as to CRUD. What if the user changes the playlist, deletes it, etc. In essence one would need to turn html pages into the equivalent of database records.

From a cost/benefit perspective this is ROUGH. If we have 100,000 playlists created daily do we now have to publish and maintain 100,000 web pages? The answer is YES. That is a very expensive proposition that seems to ignore the power of the web to create content on the fly via parameters and scripts. Having to create static content was a deal breaker for my company after many emotional meetings.

Our chief architect stormed out muttering something about the "tail wagging the dog." For what it is worth my thoughts are this is a business decision that must be made depending on your business model.

Publishing Objects

Open Graph Objects are simply your web pages with Open Graph meta tags.

Generating Facebook Open Graph meta tags dynamically