On 9 December 2011 00:09, Yuri Z <[email protected]> wrote: > I don't think that Linky should be implemented as robot/robot agent. I guess > you can just register > listener on update events and then insert the link annotation whenever text > in the edited blip looks like a URL.
I have now closed the review request for my attempt at implementing it in the EditorUpdateEvent, mostly because of the inability for it to scale well here. This is a problem mostly because it is a client side check (so implemented in JS -> which is already at its limit in most browsers from the rest of the WIAB code). The fact it is client side, would also prove a problem when an attempt at making UI more suitable for mobile browsers is started, because the link detector is (with 6/7 links) capable of maxing out a couple of cores of my desktop machine, let alone a much less powerful mobile device. If only it was as simple as 'looks like a URL'! My initial thought was to hit it with a regex, but that would scale even worse than the current code because of all the back-tracking any attempt would likely end up doing. I do think that moving the link checking server side is the best solution. Moving it to a robot also gets it out of the core code (which it isn't), and allows it (in the event it is servicing lots of user's blips) be moved to an alternate server (without needing to wait for an external Wave Bus to be implemented in WIAB). Implementing so that robots be auto-added as a participant to a wave, and hiding it from the participants list isn't particularly difficult, so I am interested in why you said back here that you "don't think Link should be implemented as a robot"? Personally, I don't see anywhere better suited to put this sort of feature. Ali
