Mike,
I think you're doing it right. Unless you want that data to be in the
URL (perhaps) or sent page to page in post data (probably a bad idea)
sessions are your best option.
-David
On Oct 2, 6:16 pm, adelaide_mike wrote:
> Hi
> In my app the user needs to drill down through a series of temp
The built-in Django development server handles 404s and 500s, but when
you deploy onto mod_python or mod_wsgi, you need a 404.html and a
500.html.
On Oct 2, 4:52 am, Gustavo Senise wrote:
> Hey Mak,
>
> I understand that. The point is that locally the app is running fine! So how
> can I understa
Guillermo,
It is possible to have a model in one application have a foreign key
to another application as of Django 1.0.
From:
http://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.ForeignKey
---
To refer to models defined in another application, you can explic
SOAP and XMLRPC have quite a few tradeoffs, but without knowing
exactly what your setup is (other than Python/Django) I'd advise you
to go with XMLRPC. However, I'll lay out why I think so and perhaps
SOAP does make more sense for you.
SOAP is the successor to XMLRPC and some people -- notably pe
Gustavo,
I believe this is a problem (feature?) of jquery. It is not
serializing your full settings object to a string. Instead, it creates
a series of url-encoded key value pairs. It looks like it is just
calling .toString() on the value side as well. When .toString() is
called on:
{"id": {"lab
According to the jsonrpc 1.1 working draft, the request type and
response should be application/json not application/javascript. Even
if you handle requests that are in other types for compatibility, you
probably want your responses to be the correct type.
http://json-rpc.org/wd/JSON-RPC-1-1-WD-2
6 matches
Mail list logo
