Al 30/03/13 19:25, En/na Parin Porecha ha escrit:
Yes, I meant the former ( managing presentation on the client ).
Also, considering that a user might have as many as 100 - 200 tasks in
one JSON file ( their description, dates, tags and all ),
is it better performance wise ?
The responsiveness
If you don't use the ORM, Forms, and even the templating system you're
losing quite a bit with Django. In my opinion, it's not worth using Django
for those sorts of projects.
While not a Python project, I found NodeJS & node-restify a good candidate
for these types of applications. That's not a co
Yes, I meant the former ( managing presentation on the client ).
Also, considering that a user might have as many as 100 - 200 tasks in
one JSON file ( their description, dates, tags and all ),
is it better performance wise ?
On Sat, Mar 30, 2013 at 11:46 PM, Alexis Roda
wrote:
> Al 30/03/13 16:
Al 30/03/13 16:41, En/na Parin Porecha ha escrit:
Thanks !
Okay, so i am dropping the idea of using JSON for storage.
So, if I use JSON only as a format to send data
to client ( All the parsing will be done client side ), is it better
than using {{ task.name }}, {{ task.start_date }} ? ( Sorry
Thanks !
Okay, so i am dropping the idea of using JSON for storage.
So, if I use JSON only as a format to send data
to client ( All the parsing will be done client side ), is it better
than using {{ task.name }}, {{ task.start_date }} ? ( Sorry to ask
this again, but i haven't got it )
On Sat, M
Remember: Premature optimization is the root of all evil.
Use a database for its intended purpose: storing data.
If you use individual files then you need to implement your own locking,
writing to disk, caching, and so forth.
Not only is the database more functional, but it will likely be more
Thank you all for your prompt replies :)
> IIUC you can't return the query (as a python object) to the client. You must
> convert the data on it to some format (json, xml, ...) that the client
> understands. That will depend on the libraries that you use in the client
> side.
So, if I don't us
You almost certainly don't want to use JSON as your storage method. This is
a database problem, and the Django ORM really shines at letting you solve
it without having to think super hard about database modeling. You wouldn't
create a table for each user's task list. You would create a model cal
Al 30/03/13 14:37, En/na Parin Porecha ha escrit:
Also, would it be beneficial performance wise ?
It depends on how you implement it:
* on a "traditional" client/server application I think that
loading/parsing/processing/encoding/saving the json file on each request
will be very expensive co
On Sat, Mar 30, 2013 at 9:42 AM, Alexis Roda
wrote:
> Yes, just import json and work with it, but be aware that you'll loose most
> of the functionality that makes django so productive: no ModelForms, no
> ORM/Querysets, no admin for tasks, ...
>
That's true. Without the ORM and Forms/ModelForms,
Al 30/03/13 14:14, En/na Parin Porecha ha escrit:
Hi,
I have just started using Django. I want to create a to-do task
manager application. Users would register, login and can work with
their tasks. So, instead of creating a table in the database for each
user, I want to create a JSON file for ea
Also, would it be beneficial performance wise ?
One more doubt -
is it better to convert query results ( obtained from sql tables ) to
JSON, and send it as an http response to the client and use it to show
data, or to simply send the query result to the client and show it via
task.name, task.start
Django is just Python, so yes. Just use the json module in the standard
library.
On Mar 30, 2013 9:23 AM, "Parin Porecha" wrote:
> Hi,
>
> I have just started using Django. I want to create a to-do task
> manager application. Users would register, login and can work with
> their tasks. So, instea
13 matches
Mail list logo
