I would like to ask for your opinion guys... I am building a prototype client-server architecture using the semantic web. I have decided to make a thick server (Server does all the semantic related stuff using Jena (querying, instantiating, storing)) and a very thin Android mobile client (client sends request with parameters and receives response). My assumption is that this will still be feasible even when I have hundreds of clients (not tested).
*1. My question is, in a design like this where hundreds of clients will access the server --- since it uses a knowledgebase and not an RDBMS (it will be slower) --- is it practical to create a fat/thick server? or should I take some load off the server and put it on the client side e.g. using AndroJena for Android so some processing will be done by the client as well. Carefully planning this part is crucial since it will be time-consuming to refactor code from server to client and vice-versa. (note Android phones are multi core phones which can means they can also do some heavy lifting)* *2. Since AndroJena does not have an active community, not like this forum... are there any better alternatives for Android? I have checked the SWIP link *http://swip.inrialpes.fr/ *it looks like there is still so much to do and not a single robust API like Jena.* * * *3. Since I am also working on the iPhone, are there anything similar to Jena out there? Probably Redland (although I haven't tested it yet)* * * I really like Jena, I have tried resorting to RAP once (tried a PHP server) but documentation is poor and it looks like its deserted already. I am happy to be a part of this community. Cheers, Daryl
