DjangoBot: #django

unlink: tie wants an upload progress meter... probably like YUI does

PAY ATTENTION

MODEL field or FORM field

christ

they're both fields

so saying "field" IS NOT a valid answer

FunkyBob: i mean, it's not solved if one server going down can take down the whole site

FORM field then.

finally

magus chill out man its just irc

im on your side but man youre going to have a coronary

unlink: it IS solved, it just involves more than slony

FunkyBob: for me, that's the master db

ned: shut it

unlink: as FunkyBob said, I am trying to do a progress reporting via an ajax call

unlink: slony has failover mechanisms... the trick is getting all the DB clients to switch their write db

i see no info in docs ;/

zbyszek: because you aren't looking very hard

http://www.djangoproject.com/documentation/newf... and http://www.djangoproject.com/documentation/newf...

unlink: and THAT is done using an off-the-shelf tool

hey look at that, right in "core field arguments" for one

hmmm... should this be possible... Timetable.objects.filter(subject.class_group="the_class_group").order_by('time','day')

FunkyBob: hmm, i guess i'm new to the game

DaveyJoe: not with that syntax of course

subject is a foreign key of the Timetble model

unlink: it's ok.. so was I a year or so ago

Thanks Magus

thnx Magus-

unlink: if you have a couple of machines you can test with, I'd love to hear someone elses experience with cybercluster

tie: you could have the client ping the server every now and then

unlink: yeah, that's the idea, but how will the server know what to respond?

unlink: the upload thread would need to periodically update some globally accessible progress counter

tie: have it pass some sort of key in the query param

and Django doesn't work that way

Ich Bin Dein Gummibaer! :D

FunkyBob: it depends what the progress is of

ESSEN!

FunkyBob: nuu

FunkyBob: yeah, HTTP is stateless

*runs away from being eatten*

unlink: the client doesn't know the status... one server-side process does the job, and only it knows the status

the trick is to share the status information with other requests/views

FunkyBob: anyway, my "couple of machines" at the time is a bunch of UML instances on a laptop with 512M of RAM O:-)

tie: yes, what are you monitoring the status of?

tie: personally, I'm in favor of experimenting with a custom XHR FTP :) but that'd require JavaScript having random access to the given file

unlink: a file copy operation

unlink: worth a shot :)

FunkyBob: well i'd love a couple more gigs of RAM, but yeah :P

FunkyBob: what's your email, i'll send you a holler when i test it out

FunkyBob: I am not sure what exactly do you mean by "XHR FTP"?

unlink: you logged in?

FunkyBob: logged in to what?

tie: XHR == XmlHttpRequest... how most AJAX is implemented

tie: FTP == File Transfer Protocol

unlink: freenode... so I can prv msg you

ok, so how do you mix them?

you mean calls to ftp:// urls?

FunkyBob: yep

anyway, I guess your idea is to save progress to a file, which is kinda i/o intensive, but yeah, it's a soution

FunkyBob: erm, its the other way around ;)

you have to be logged in to send, not receive

(unless the other one is set unfiltered)

the best idea I go so far are scheduled DB updates

Magus-: ok... never was sure

thanks

for clearing that up

hmm would be nice if there was an easier way to add management commands, rather than app/management/commands/command.py something like settings.MANAGEMENT_COMMANDS=(('command','klass'),)

that's not easier

Isn't it better to not have to manipulate settings just to add functionality?

requiring a settings edit would be silly - you'd have to edit it every time you grabbed a 3rd party app with commands

the current method just works

you add the app to INSTALLED_APPS and hey look, custom command is ready

i know, but it's a pain when you just want to add a simple command that doesn't really a pply to an app

How about simply making it a script to execute?

indeed

Without going through the management mechanism?

it's more fun this way

request.method aways returns 'GET' ?

zbyszek: When the request method is GET, yes...

zbyszek: if it's a GET request, of course

obviously it won't return GET on a POST

Magus-: what when there is GET and POST ?

huh?

you can send form (post method) to ?foo=bar

then method is POST obviously

The use of a query string doesn't mean a request is a GET.

method is the method, it has nothing to do with data sent

POST /foo/?bar=baz HTTP/1.1

that may use a querystring, but it's a POST request, obviously

so naturally method is POST

even though there's data in request.GET

oh

Which has always been a pet peeve of mine about web development.

Everybody seems to put query string data in a structure called 'GET'.

that is imho good becouse you can send a link to a friend

Yes, query strings are fine. That's not my point.

you completely misunderstood, zbyszek

But they're not "GET data" the same way one thinks of "POST data"