Hi all,
Did a quick test (based on Java serialization - most vendors will have
optimized this fat format) using a Detail object with 10 Integer public
fields and an Array of 10 Integers. Here are the results for the
serialization where n = 10000 (array size) and m = 10 (Integer's).
Stream size
========================
OO : 1060304
Table : 1100144
increase in Table test of 3.75%
Performance Overhead (Average of 15 executions)
========================
OO : 2325 ms
Table : 2310 ms
No real increase or decrease
kind regards,
William Louth
> -----Original Message-----
> From: Louth, William (Exchange)
> Sent: Wednesday, April 26, 2000 7:49 PM
> To: 'A mailing list for Enterprise JavaBeans development'
> Subject: RE: Cached Rowsets-do we need to use them
>
>
> I have a question regarding the performance overhead associated with
> sending N number of Detail objects which have M numbers of fields compared
> to sending N x M number of strings, either can be trasnmitted in an array
> or collection. I suspose this all comes down to the serialization format.
> I will attempt to test this tommorrow - the engineer in me speaking now.
>
> kind regards,
>
> William Louth
>
> -----Original Message-----
> From: Louth, William (Exchange)
> Sent: Wednesday, April 26, 2000 7:07 PM
> To: 'A mailing list for Enterprise JavaBeans development'
> Subject: RE: Cached Rowsets-do we need to use them
>
> Hi Sesh,
>
> Personally I do not believe in database-like view of the world that is
> constantly being advocated in list and tabular server operations. What you
> typically see is an collection of objects on the server side being
> transformed into an array x array of strings before transmitting to
> client. What happen to OO? I prefer to send my domain objects (State or
> Details objects, whatever you call them) to the client and rely on an good
> OOUI to solve the problem of mapping each object into what component it
> needs to be displayed in. I have an article coming up in JavaReport
> detailing how to better solve this great divide titled "Bridging the gap
> between Java Clients and Enterprise Java Beans using XML". To me OO
> concepts should be brought more and more into the design of client
> interfaces - please do not reply regarding widgets.
>
> kind regards
>
> William Louth
>
> -----Original Message-----
> From: Sesh Kumar Jalagam [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, April 26, 2000 6:28 PM
> To: [EMAIL PROTECTED]
> Subject: Cached Rowsets-do we need to use them
>
> Hai how is every one listing the data from the entitybeans. Does any one
> use Cachedrowsets. I tried to use them but I was only able to use them
> with BMP's . I couldn't find any way to convert an Enumeration to
> CachedRowset.
>
> The method i am following to list the data to the users is by collection
> of immutable objects (JavaBeans. with only getter fields).Are there any
> other better ways to do this (
> <http://www.ejbnow.com/ejbtips/ejbtip_4.html)>
>
> I want to know how others are doing this
> Thank you
> Sesh
***********************************************************************
Bear Stearns is not responsible for any recommendation, solicitation,
offer or agreement or any information about any transaction, customer
account or account activity contained in this communication.
***********************************************************************
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
