On Wednesday, December 14, 2011 8:58:23 PM UTC, jason wrote: > > > So maybe this is where my confusion lies. If I make two sucessive posts > > to the /eval url, should they > > a) both have the same session_id and two different msg_ids, or > > b) always random session and msg ids (4 random UUIDs for 2 requests)? > > (b). They should certainly have two different session ids. The message > ids should be unique across all messages, so those should be unique too, > though I suppose maybe you could make the argument that the message ids > need to be unique just inside a session (but that's not what we assumed, > so I'm not sure if it will work). > > Think of it as a routing protocol. The session id routes to the correct > Sage session, while the message id is just a unique identifier for the > message itself. > Thats precisely how I thought about it, but you keep telling me that its not. Since I want to use the same sessions (that is, have a history and variables) I though I should be setting the same session UUID for subsequent eval calls. But you keep telling me to use different sessions for each call, so I'm not routing anywhere but, rather, get a new instance every time.
I didn't know that one can use JSON in the eval request, I'll give it a try. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
