Development

#1126 (add autodiscovery thing to sfWebResponse)

You must first sign up to be able to contribute.

Ticket #1126 (assigned enhancement)

Opened 2 years ago

Last modified 1 week ago

add autodiscovery thing to sfWebResponse

Reported by: pookey Assigned to: FabianLange (accepted)
Priority: major Milestone: 1.2.0
Component: other Version: 1.1.0 DEV
Keywords: Cc: pookey@pookey.co.uk
Qualification: Design decision

Description

http://www.symfony-project.com/forum/index.php/t/3778/

would be really handy to have this...

the assset helper already has a auto_discovery_link_tag() function, however... if you want to have different feeds on different pages you can't really use this as is.

I would suggest that a system is added so that you can add diffent <link type="alternative...> in view.yml and it from $response->addAltLink() (althoguth I don't like that function name)

Change History

11/23/06 06:29:05 changed by pookey

it seems firefox will pick up the <link rel="alternate"..> tag even when it's not within <head> section. Is that valid XHTML? Does IE7/Opera also preform like that?

Even so... does this invalidate this ticket?

12/02/06 10:32:03 changed by pookey

  • priority changed from minor to major.

IE7 will not detect this outside of the header, so raising priority

12/16/06 16:40:49 changed by fabien

  • milestone set to post-1.0.

10/01/07 07:04:25 changed by dwhittle

  • owner set to fabien.
  • component set to cache.
  • qualification set to Unreviewed.

Can you provide a patch?

12/26/07 22:38:23 changed by fabien

  • component changed from cache to other.

05/10/08 22:36:11 changed by fabien

  • milestone deleted.

06/23/08 07:04:58 changed by dwhittle

  • version set to 1.1.0 DEV.
  • qualification changed from Unreviewed to Design decision.
  • milestone set to 1.2.0.

08/20/08 09:20:12 changed by FabianLange

  • owner changed from fabien to FabianLange.
  • status changed from new to assigned.

Old ticket, but I am sure pookey will reply.

Whats the % ratio of use cases where this will be done for feeds and for something else. My current asumption is that feeds are the 80% use case

So I would work on this, but naming the Method and yaml option Feed(s) Would that be sufficient in your opionion?

09/26/08 21:52:21 changed by pookey

I think you're right, I imagine even higher then 80% is feeds.

I think the name in this case is reasonably irrelivent, I'm happy with auto_discovery/AutoDiscovery being used, I don't mind typing a few extra chars :)