If you are sending such large amounts of data perhaps a layer providing compression / decompression would be a good idea. Also, I imagine that this would significantly reduce the size of XML as a lot of it's verboseness would be repeated symbols.
-----Original Message----- From: James Sugrue [mailto:[EMAIL PROTECTED] Sent: Monday, February 16 2004 4:50 p.m. To: 'NZ Borland Developers Group - Delphi List' Subject: RE: [DUG] n-Tier Architechure advice I've had a look at kbmMW, but nothing much more than that. Its not really a business object layer, more of a interface between the data and the UI, but I want the data to be independent in tier 3 and have it standard in tier 2. I.E I want RDMS independence at data level but have something standard talking to the UI layer, such as a clientdataset or kbmMemTable. Its will be fairly small amounts of data, other than one file (product file) which will always be around 30k records. It appears that the bulk of the time isn't copying data between sockets, but creating the data in the kbmMemTable and saving to a stream. I have a couple of other options I could look at, but if any one else has done this sort of thing before and has some war stories, that would be great.... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neven MacEwan Sent: Monday, 16 February 2004 4:07 p.m. To: NZ Borland Developers Group - Delphi List Subject: Re: [DUG] n-Tier Architechure advice James XML will always be big as it is verbose, have you looked at kbmMW? If you are looking at 30K records then you are going to need something that does Fetch on Demand, Also I'd rethink your business objects. are there really business objects that have 30,000 items? HTH Neven ----- Original Message ----- From: "James Sugrue" <[EMAIL PROTECTED]> To: "'NZ Borland Developers Group - Delphi List'" <[EMAIL PROTECTED]> Sent: Monday, February 16, 2004 3:42 PM Subject: RE: [DUG] n-Tier Architechure advice > Have been playing today and have decided the best way is to use sockets to > connect between tier 2 and tier 3 and pass a stream to a kbmMemTable. This > works really well for small to medium sized datasets, but bigger ones can be > slow, i.e around 1 minute for 30K+ records. > > > > Has anyone else done this in the past? Any way to speeds this up, or would I > be better to send XML between sockets? The XML file would be around 30Mb > anyway which I would imagine would be slow too. > > > > _____ > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of James Sugrue > Sent: Monday, 16 February 2004 8:35 a.m. > To: [EMAIL PROTECTED] > Subject: [DUG] n-Tier Architechure advice > > > > Morning all, > > I am about to upgrade an app that has a BDE/Paradox backend. > > In the new app I want a UI layer, data class/business rules layer, a > physical data layer, and another layer which talks to another third party > app which is the source of the data. > > I was thinking of using XML to talk between tiers 2 and 3, and using > ClientDataSets to represent the data in tier 2. > > I was just after some advice on how other people do n-tier apps, pit falls > etc. Maybe a URL or two with examples would be good to get me started. I > only use Pro level Delphi, so Midas etc isn't an option at this point. > > > > > > Cheers > > > > ------------------------------------------------------------------------ ---- ---- > _______________________________________________ > Delphi mailing list > [EMAIL PROTECTED] > http://ns3.123.co.nz/mailman/listinfo/delphi > _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
