> Okay, cool, I can see now what you are thinking of. > > Starting out, I'd make a module, gem, engine, whatever you choose, > that just allows you to test out the API; keeping it in it's own space > will help keep your application modular; you should consider the Pulp > service and your API wrapper to be a separate service from the rest of > your app, which it is. You don't need to worry about database models > at this point unless they help you test your wrapper, and views can be > very rudimentary (even displaying just structured JSON might be > enough).
Okay, I understand this, But do you know any application already written ... something similar, i can take example from ? .. > However, if that *is* the case, and all you are doing is packaging up > requests from a client, forming a Pulp API call, then doing something > back to the user with the results, why not go with something like > Sinatra, or another light-weight stack? by writing this, i want to understand rails concepts and at the same time help my users to provide some GUI .. i never looked at Sinatra . but i will try .. but will be greatfull if you have some example ( it might doesnt make sense to ask you for example may be ..but nothing wrong in asking :) ) Regards, DJ -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
