it is pretty easy to interface a web server with your server through the API. It is rediculously dificult to parse your main web site and interface that way. Unfortunetly your API has some majer restrictions which are keeping me from going public with my web site.

Major Problems:
1) No way to get hash code of hidden models. Need a findURL or findHash function.
2) No way to upload stl files larger then 16MB.

Minor Problems:
3) No way to restrict material types
4) No way to alter product pricing(If I could get 1 I could parse the page check the price is correct but even then I could not alter it. My pricing is usually +-2cents do to rounding errors)

The 195 dice I uploaded today were designed with Alibre bulk uploaded to my FTP server then wrote a script to quickly upload the entire batch to your server as it would have taken all day to manually upload through your interface.

As for what my web site it consists of 4 parts:

1) site code, lets user see initial page. This code runs once per page reload
2) ajax back end - handles interface between demons and the site code. Lets user see what is going on
3) render demon - This demon sits on server and takes render job cue and renders the jobs in order. I do jobs sequentially instead of in parallel so that the server does not crash from high load and so if the user leaves my site the job will keep going and I can send an email when it is done.
4) upload demon - This demon sits on server and uploads all finished rendered jobs sequentially to the server. I am doing these sequentially because I have a multi gigabit backbone connection and could probably take down shapeways if I tried to upload say 195 files in parallel.

Follow me on twitter http://twitter.com/mctrivia or my blog at http://4ddice.blogspot.com/