Yep the jsonBatch interface wen't away with the latest updates (we're using the spec'd json-rpc protocol now which lives under social/rpc). it sounds as if either you haven't cleaned your cache (/tmp/shindig under *nix), or your shindig/config/container.js file hasn't been updated due to local changes (and thus still has the old end point configured).
On Thu, Oct 30, 2008 at 6:40 AM, Brandon Peters <[EMAIL PROTECTED]>wrote: > I recently updated my Shindig installation using 'svn update' from > revision 685138 to the current revision. I've updated my data handler > based on the changes, and I also updated my configuration files. After > trying to get everything to work, I now run into this error: > > <h1>500 Internal Server Error - Internal Server Error</h1> > Invalid or unknown service endpoint: > jsonBatch?st=NEM2eGE0bTNKJTJGcGtDZUYxRDNJVzNLQjR1JTJGbWNUcTF0dE > > 96YTJiTWZxZlB3eTBROUllZ05pdVhENiUyRiUyRmF1NWE4VWI3WFJNek13b0VvRkMwMFg4Z1NKWlNCdDRpSEVjUTdCbmZHcWNlel > > JobyUyQjFtN0xQaHd6dEVPZ2xOZUlYaXFoSExMRzM0Z3plU1VaZ2pSZkVWbExHV05QJTJGTDdjSGlLTlN0emxOVW9YV2pGJTJCalFkMnBOaktiJTJCbTYwVlBnQWplWDljckROR0JUaEhFRlZpZnJpYjV1RjNWQWVucyUzRA > %3D%3D > > I'm using the PHP version of Shindig. Any ideas? > Brandon > > > -- > Brandon Peters >
