JSON is probably the way to go for your clients accessing the custom DB layer..
Check out http://code.nytimes.com/projects/dbslayer and http://halcyon.rubyforge.org/ Aman Gupta On Jan 31, 1:09 pm, Angel <[EMAIL PROTECTED]> wrote: > Look up RESTful web apps. Specifically for examples of how this would > work look up Flex on Rails or Flex w/ merb. Merb works well with > sequel. > > Not to start a flame war or anything, but you may be more interested > using Ruby on Rails and its contained ActiveRecord ORM, since merb > +sequel is newer and more of a do it yourself framework. > > -angel > > On Jan 31, 3:57 pm, ivanb <[EMAIL PROTECTED]> wrote: > > > I have the following scenario in mind: > > > I have DB, app server and gui client, each on individual machine. > > Client can talk to app server via http, app server can talk to DB. > > > 1. client call GetCustomers on app server > > 2. app server goes to DB (only app server has access to DB > > 3. app server returns dataset, array or collection of customers to > > client > > 4. client modifies collection, adds new customer, or modifies some > > customer > > 5. client calls UpdateCustomers on app server > > 6. app server goes to DB and updates > > > The key point is that client doesn't have access to DB. > > I could create two classes, Customer < SequelModel and CustomerNTier, > > and copy variables between them. I couldn't pass Customer directly to > > client, since client doesn't have access to DB and all updates must go > > through app server. > > > On Jan 31, 7:37 pm, Aman Gupta <[EMAIL PROTECTED]> wrote: > > > > DB1 = Sequel.sqlite 'one.db' > > > DB2 = Sequel.sqlite 'two.db' > > > > class ModelOnOne < Sequel::Model(DB1[:table]) > > > end > > > > class ModelOnTwo < Sequel::Model(DB2[:table]) > > > end > > > > Aman Gupta > > > > On Jan 31, 3:12 am, celldee <[EMAIL PROTECTED]> wrote: > > > > > Hi Ivan, > > > > > Sequel is an ORM. As such, it allows you to perform various database > > > > operations via Ruby libraries. It's up to you how you use it in an n- > > > > tier environment, but whether you use it or not will depend on the > > > > software stack that you have (or are allowed to have) in your target > > > > environment. > > > > > So, Sequel would be used as a component of your n-tier environment in > > > > whichever tier is appropriate. Do you have a particular scenario in > > > > mind? > > > > > Cheers, > > > > > Chris > > > > > On Jan 31, 10:24 am, ivanb <[EMAIL PROTECTED]> wrote: > > > > > > Anyone? > > > > > > On Jan 20, 8:49 pm, ivanb <[EMAIL PROTECTED]> wrote: > > > > > > > Does sequel supports n-tier applications. > > > > > > That is, DB --- aplication server --- client. > > > > > > > Thanks- Hide quoted text - > > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
