Henning Hraban Ramm wrote: > Dear wizards, > I'm a bit stuck with my application design: > It's a local client for a web application, an exporter that writes web > articles to InDesign files. > It pulls the data read-only as JSON from a web service - the source database > is only accessable on the web server. > The web service provides not only the article data but also structural stuff > like issues and categories. > My dabo GUI should fill some dropboxes with that structural data to select > from. > > So I've > - a connection (https with session ID) > - a "bizobj" (data conversion, sorting, filtering) > - a dabo GUI > Looks like 3 tiers, doesn't it? > > So I'd like to know if I can use dabo's grace also for the first two tiers > in any way, or only for the GUI. > I've still no experience with dabo, so I can't guess which classes would be > general enough to inherit from. > > I *don't* need help with JSON conversion or session handling, just hints > which dabo classes would be suitable ancestors. Or what I should construct > in an other way. >
I both agree and disagree with the current replies :) to use dabo's Biz objects, you need a data object to talk to that conforms to dabos Data tier api. you 'can' create such a thing, but it may be be quite a bit of work. (and assuming that the dabo tiers are well separated, which I think they are) take a look at dBackend and the various subclasses of it: dbMySql, dbFirebird... Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
