Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 397959598 for ; Mon, 27 Feb 2012 08:41:24 +0000 (UTC) Received: (qmail 63766 invoked by uid 500); 27 Feb 2012 08:41:23 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 63625 invoked by uid 500); 27 Feb 2012 08:41:23 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 63584 invoked by uid 99); 27 Feb 2012 08:41:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Feb 2012 08:41:21 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of olegsivokon@gmail.com designates 209.85.210.175 as permitted sender) Received: from [209.85.210.175] (HELO mail-iy0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Feb 2012 08:41:12 +0000 Received: by iaby12 with SMTP id y12so6347070iab.6 for ; Mon, 27 Feb 2012 00:40:51 -0800 (PST) Received-SPF: pass (google.com: domain of olegsivokon@gmail.com designates 10.50.159.161 as permitted sender) client-ip=10.50.159.161; Authentication-Results: mr.google.com; spf=pass (google.com: domain of olegsivokon@gmail.com designates 10.50.159.161 as permitted sender) smtp.mail=olegsivokon@gmail.com; dkim=pass header.i=olegsivokon@gmail.com Received: from mr.google.com ([10.50.159.161]) by 10.50.159.161 with SMTP id xd1mr10020544igb.15.1330332051970 (num_hops = 1); Mon, 27 Feb 2012 00:40:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=+oYWmbsuiNc3egf1q1wzmXQViszcGFF0Kbl3L2LCmNo=; b=HGPmvgjBSNq2iGh8tuHGmK9d+T6hHxSO1xpsKz6+3VhzSYVxnDHvRNyuI8T8ZRyMgr PzXdFb5ezKIoxEpUHfZ0Y1zfLsOViYUQn2NIcGmmJ1HCwFZaxRYk4NXh1jyRGy2YtdBC zAm0C07z3Y7qRcPbw2TCzO8zWQ9yo+cTDryZA= MIME-Version: 1.0 Received: by 10.50.159.161 with SMTP id xd1mr8221522igb.15.1330332051934; Mon, 27 Feb 2012 00:40:51 -0800 (PST) Received: by 10.42.224.132 with HTTP; Mon, 27 Feb 2012 00:40:51 -0800 (PST) In-Reply-To: References: Date: Mon, 27 Feb 2012 10:40:51 +0200 Message-ID: Subject: Re: SEO for SWF Was: Flash Platform roadmap From: Left Right To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=14dae9340b93638cd304b9ee11a6 X-Virus-Checked: Checked by ClamAV on apache.org --14dae9340b93638cd304b9ee11a6 Content-Type: text/plain; charset=ISO-8859-1 > find ways to make it easy to sniff a SWF for searchable text That would be easier if the rendering of SWF was be an entirely separate program. Then, companies, who are interested in searching the output, would be able to "see" what has been actually shown to the user. But there's a huge difference between what users are able to see and what they actually saw. I.e. almost every portfolio kind of site has an "about us" page, where people put the biography of their CEO and some other random stuff nobody cares about (well, maybe the CEO does...). An automatic crawler wouldn't be able to replicate human behavior if they follow the tab index... besides, Flash, especially Flex application have a tendency to completely mess up the tab indexing, so that parts of application become completely inaccessible through it. Then there are things like scrolling... But when you think of all input modes available on touch screen devices... so, again, probably, the crawler would have to know what are the built-in input events that have registered handlers and then try to pipe these events to see what happens in response... Imitating drag events? sounds like mission impossible, if the scenario is to drag something to a particular spot in order to initiate some interaction. Either Google comes up with a Skynet-like crawler, or that isn't going to happen :) It sounds like it's really cheaper to hire labor force in the third world countries and ask them to write a report on what they saw on the site, then to write an intelligent crawler :D --14dae9340b93638cd304b9ee11a6--