Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

chosen and configured) since the REST API adds a layer of HTTP based exchanges. Regards Eric From: django-users@googlegroups.com on behalf of Tyler Lynch Sent: Saturday, October 27, 2018 7:12:13 PM To: Django users Subject: Re: Should I use Django-Rest

Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

ifique et Technique du Bâtiment > 290 route des Lucioles - BP 209 > 06904 SOPHIA ANTIPOLIS CEDEX > http://www.cstb.fr > > -- > *From:* django...@googlegroups.com < > django...@googlegroups.com > on behalf of Tyler Lynch < > tyler...@gmail.

Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

Hi Andréas, thanks again for the response. I've decided to take your advice and not going to be adding DRF because I simply don't need an API, so no need for the added complexity. It's funny that you suggest using pandas for the csv import/exporting though. I kept seeing pandas mentioned

Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

To: Django users Subject: Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API? Hi Eric, Thanks for the response You mention that adding DRF can actually make you lose some potential benefits from caching? Might i ask how that i

Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

Hi again, I don't think there is any performance reason to add DRF. You should architect your application in a way that the database is the main speed issue (for example, avoid doing loops in python) - then you can add som caching to the queries that you know can be cached. That would give you

Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

t; > > Regards > > > Eric > -- > *From:* django...@googlegroups.com < > django...@googlegroups.com > on behalf of Andréas Kühne < > andrea...@hypercode.se > > *Sent:* Friday, October 26, 2018 9:29:40 AM > *To:* django...@googlegroup

Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

Hi Andréas, Thanks for getting back to me! I guess adding DRF to my project right now would be a case of premature-optimization then. I had a bit of muddied thinking such that I thought DRF might help with caching the database queries, but I guess that is completely independent of DRF? Is

Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

From: django-users@googlegroups.com on behalf of Andréas Kühne Sent: Friday, October 26, 2018 9:29:40 AM To: django-users@googlegroups.com Subject: Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API? Hi, I really don't get why

Re: Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

Hi, I really don't get why you would want to do that? If you are doing only a "standard" website - you don't want or NEED the extra complexity of running DRF. It's not that DRF is hard to setup - but for example if you want to present a list of items - in "standard" django, you create the list

Should I use Django-Rest-Framework for performance reasons, despite not needing an externally-consumable API?

I have no need for an externally consumable API, but I am interested in using Django-Rest-Framework simply for performance reasons. I'm led to believe that by decoupling my front and back end and then simply consuming the DRF api within views, that I can setup a better caching system? Does

Re: should i use django

Oh, also, as you sound like you're a coder, the thing I normally try and sell my desktop-side friends to django for web development is that you have the entire python library sitting there for you. You can code however you like, the way you like. You just need to remember that your eventual output

Re: should i use django

If you dont really need to do anything web specific bar displaying some XML you could use something like cherrypy - its a python framework for building web apps very much from the ground up. That said, it's so easy to use django to handle a few urls and it won't add much overhead so it's a fine

Re: should i use django

On Jul 16, 9:56 pm, gary_p wrote: > On Jul 16, 7:46 pm, uday wrote: > > > Hi, > > >    I need to design a simple web app that would mostly display data > > from an xml file in different forms(like graphs,charts etc) after some > > processing.I have to

Re: should i use django

Udayan, I think you're on the right track. While Django can handle big sites, Django works well for small projects, too. Also, you may find it helpful having a big community around to answer questions. I recommend using the admin site, especially if you need to support having users log in. Feel

Re: should i use django

Udayan, This can all be easily be done in Django if you were already familiar with it. However, if you are starting from scratch with both Django and Python it will take you two weeks just to get a handle on one of these. I'm sure you can do it, but not within two weeks. I've been working with

Re: should i use django

On Sat, Jul 17, 2010 at 7:26 AM, gary_p wrote: > I read data from instruments, and/or > enter parameters by hand, then run an app that crunches the data > producing graphs and, in my dreams, animations. Can Django do this > smoothly? Sure. But, when you are doing charts

Re: should i use django

On Jul 16, 7:46 pm, uday wrote: > Hi, > >    I need to design a simple web app that would mostly display data > from an xml file in different forms(like graphs,charts etc) after some > processing.I have to do this in two weeks >    I don't have any web development

should i use django

Hi, I need to design a simple web app that would mostly display data from an xml file in different forms(like graphs,charts etc) after some processing.I have to do this in two weeks I don't have any web development background.I am more of a systems programmer and thus use C/C++ a lot.But

Re: Should I use Django?

I thought I'd tell you: I decided to switch to Django/App Engine. :) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To

Re: Should I use Django?

It's all relatively simple stuff, I guess... Thanks. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this

Re: Should I use Django?

2009/3/8 Wiiboy : > >> Is there any reason you should'nt? Plain CGI code sounds quite old >> even for me ;) > > I'd have to rewrite everything. :( It depens on your code. Perhaps you can reuse the logic and just write the urls and views. Just check Django, I think it's worth

Re: Should I use Django?

> Is there any reason you should'nt? Plain CGI code sounds quite old > even for me ;) I'd have to rewrite everything. :( --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group,

Re: Should I use Django?

2009/3/8 Wiiboy : > > Hi guys, > I'm making a small site (small for now, at least), that isn't quite > finished yet.  I'm the only one who is writing server-side code. > Presently, I'm writing straight Python code, through CGI, on a shared > hosting provider.  Is there any

Should I use Django?

Hi guys, I'm making a small site (small for now, at least), that isn't quite finished yet. I'm the only one who is writing server-side code. Presently, I'm writing straight Python code, through CGI, on a shared hosting provider. Is there any reason why I should use Django on my site, on the