I am averse to doing that because I have offline bookmarks like the Python documentation also which contain a lot of links. If I rendered it as text then this problem will go in an loop. The browser will not allow any of the rendered links on that page to be opened. So a solution is needed. That is why I am considering using the fact that browser and server are on same machine. Instead of rendering the links on my search page I can instead render reference numbers which I can use to send requests to the server. Then the server will be able to use webbrowser.open for opening the required webpage. A little change will help me solve this problem.
I guess I need to thank Daniel Roseman. If he had not mentioned that client and server are on same machine explicitly I would never have looked at the possible benefits of this. I understand that this is not a good solution as this makes my implementation dependent on client and server being on same machine. I am also considering using JavaScript window.open in the onclick of the bookmark. That way it might work. Need to check. On Friday, May 23, 2014 12:24:13 AM UTC+5:30, C. Kirby wrote: > > If they are always going to be on the same machine then why don't you open > the file on the view side and render it as text to the browser? > > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a4464422-9065-4245-bb7f-26a8c70053dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
