1) Browser Client: There is no VCell Browser client. However, I recently prototyped a very limited Browser Client for searching Simulation Tasks which is served up from my prototype RESTful API (see attached image) based on the Restlet framework. The Web API currently only provides Simulation Task searching and content negotiation (HTML or JSON). I've attached a WADL file (a RESTful version of a WSDL file) which is downloaded easily by appending ?method=options to the url (see attachment for documentation of the SimulationTask api). This Web API will be expanded to search for Models, Run Simulations, Retrieve nonspatial simulation results, and other VCell uses. HTTPS is supported, but authentication has not yet been implemented ... (open for negotiation).
the a JSON representation of a query result is
[{"simKey":"81599089","simName":"Copy of EBChombo short 1","userName":"anu","userKey":"2302355","htcJobId":"PBS:1253865.master.cm.cluster","status":"completed","startdate":1366312880000,"jobIndex":0,"taskId":48,"message":"completed","site":"TEST","computeHost":"signode09","schedulerStatus":"completed","hasData":true,"modelID":"81599755","modelType":"BioModel"},{"simKey":"81113055","simName":"Simulation1","userName":"anu","userKey":"2302355","status":"completed","startdate":1365784834000,"jobIndex":0,"taskId":0,"message":"completed","site":"ANU_LOCAL_VCELL","computeHost":"\u003c\u003clocal\u003e\u003e","schedulerStatus":"completed","hasData":true,"modelID":"81113057","modelType":"BioModel"},{"simKey":"80993624","simName":"Simulation1","userName":"anu","userKey":"2302355","status":"completed","startdate":1363989414000,"jobIndex":0,"taskId":0,"message":"completed","site":"ANU_LOCAL_VCELL","computeHost":"\u003c\u003clocal\u003e\u003e","schedulerStatus":"completed","hasData":true,"modelID":"80993626","modelType":"BioModel"},{"simKey":"80988255","simName":"Copy of Simulation0","userName":"anu","userKey":"2302355","htcJobId":"PBS:1167744.master.cm.cluster","status":"completed","startdate":1363966214000,"jobIndex":0,"taskId":0,"message":"completed","site":"REL","computeHost":"signode08","schedulerStatus":"completed","hasData":true,"modelID":"81616789","modelType":"BioModel"},{"simKey":"80988255","simName":"Copy of Simulation0","userName":"anu","userKey":"2302355","htcJobId":"PBS:1167744.master.cm.cluster","status":"completed","startdate":1363966214000,"jobIndex":0,"taskId":0,"message":"completed","site":"REL","computeHost":"signode08","schedulerStatus":"completed","hasData":true,"modelID":"80988258","modelType":"BioModel"}]
This is just a first pass, too much information for the mobile client.
2) Android Client: I've also built a very simple Android App which displays a simple list of simulations from the new VCell RESTful API ... this is only a toy however. It uses the client-side Restlet framework which conveniently reuses the server's SimulationTask resource definition. (no documentation on this).
3) VCell's Traditional Desktop client is a very large Java application which communicates course-grained transactions with large complicated objects which are either serialized or represented in XML. VCell's current Server API uses Java RMI and exposes separate Remote Server Objects (via RMI) for Database Access, Simulation Data Retrieval, Simulation Control, and Administration. There is some description at http://vcell.org about the overall architecture and our VCell Client (please feel free to run the VCell Client for yourself). There are also You Tube Videos of VCell Tutorials (google "vcell youtube tutorials")
. Accessbut the production server API is RMI (Java RPC) that is not geared toward the use cases of model/web applications.
I have a prototype RESTful notclient can be launched (Java webstart) from http://vcell.org