Databases
StackOverflow2013
Postsdbo
POStrategies for "Always-Connected" Windows Client Data Architecture
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POStrategies for "Always-Connected" Windows Client Data Architecture
    primarykey
    data
    text
    <p>Let me start by saying: this is my 1st post here, this is a bit lenghty, and I havent done Windows Forms development in years....with that in mind please excuse me if this isn't directly a programming question and please bear with me as I really need the help!!</p> <p>I have been asked to develop a Windows Forms app for our company that talks to a central (local area network) Linux Server hosting a PostgreSQL database. The app is to allow users to authenticate themselves into the system and thereafter conduct the usual transactions with the PG database. Ordinarily, I would propose writing a webforms app against Mono, but the clients need to utilise local resources such as USB peripheral devices, so that is out of the question. While it might not seem clear, my questions <strong>are</strong> <em>italised</em> below:</p> <h3>Dilemma #1:</h3> <p>The application is meant to be always connected. <em>How should I structure my DAL/BLL - Should this reside on the server or with the client</em>?</p> <h3>Dilemma #2:</h3> <p>I have been reading up on <a href="http://msdn.microsoft.com/en-us/library/bb384339.aspx" rel="nofollow noreferrer">Client Application Services (CAS)</a>, and it seems like a great fit for authentication, as everything is exposed via URIs. I know that a .NET Data Provider exists for PostgreSQL, but <em>not too sure if CAS will all work on a Linux (Debian) server</em>? Believe me, I would get my hands dirty and try myself, but I need to come up with a logical design first before resources are allocated to me for "trial purposes"!</p> <h3>Dilemma #3:</h3> <p>If the DAL/BLL is to reside on the server, is there any way I can create data services, and expose only these services to authenticated clients. There is a (security) requirement whereby a connection string with username and password to the database cannot be present on any client machines...even if security on the database side is quite rigid. I'm guessing that the only way for this to work would be to create the various CRUD data service methods that are exposed by an ASP.NET app, and have the WindowsForms make a request for data or persist data to the ASP.NET app (thru a URI) and have that return a resultset or value. <em>Would I be correct in assuming this? Should I be looking into WCF Data Services? and will WCF work with a non-SQL Server database?</em></p> <p>Thank you for taking the time out to read this, but know that I am desperately seeking any advice on this! THANKS A MILLION!!!!</p> <h3>EDIT:</h3> <p>I am considering also using NHibernate as my ORM</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGeorg Fritzsche
    1. USmagz
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POStrategies for "Always-Connected" Windows Client Data Architecture
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POStrategies for "Always-Connected" Windows Client Data Architecture
      1. USShalan
      1. VTFavorite
    3. VO
      singulars
      1. POStrategies for "Always-Connected" Windows Client Data Architecture
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe URL for the PostgreSQL .NET data provider is: http://npgsql.projects.postgresql.org/
      singulars
      1. POStrategies for "Always-Connected" Windows Client Data Architecture
      1. USmagz
    2. COWhat exactly do you mean when you say "always connected"?
      singulars
      1. POStrategies for "Always-Connected" Windows Client Data Architecture
      1. USAdrian K
    3. COI mean, that unlike a Smart-Client which is occassionally connected (to a central DB server, for instance), due to the business requirements of this app, it must always be connected to live data - else it cannot allow the user to continue. "If the person is busy working with something and the connection drops for whatever reason then too bad" ... to quote our analyst! yep, thats the mentality I gotta put up with!
      singulars
      1. POStrategies for "Always-Connected" Windows Client Data Architecture
      1. USmagz
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload