Of course I did.  =)

I understand that, in reality, no one does this now.  I was pointing out
that true portability assumes that someone _might_ do this in the future.
Isn't portability one of the basic concepts behind EJB?



Jonathan Baker
Internet Applications Division
Sybase, Inc.



James Cook wrote:
>
> I don't think you *read* my reply.
>
> jim
>
> ----- Original Message -----
> From: "Jonathan Baker" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, November 17, 2000 5:54 PM
> Subject: Re: File I/O in EJB
>
> > But the point is, the container might NOT support file I/O.
> >
> > Although there are no containers that currently run on anything but
> standard
> > OS based systems, there is nothing stopping a vendor from creating a
> > 'turnkey' solution that is a box that only runs an application server.
> That
> > box might not have any understood file I/O channels, so any code written
> for
> > direct I/O would not work.
> >
> >
> > Jonathan Baker
> > Internet Applications Division
> > Sybase, Inc.
> >
> >
> >
> > James Cook wrote:
> > >
> > > ----- Original Message -----
> > > From: "Dave Wolf" <[EMAIL PROTECTED]>
> > > > Why not use JDBC.  Then if you have a JDBC driver which supports using
> a
> > > > file I/O database you use that.  Then if you have no filesystem on a
> > > > platform, you choose another JDBC dfiver in your environment mappings.
> > > >
> > > > Now you meet 18.1.2 and have true WORA of your code.
> > >
> > > I think people sometimes overstress the importance of WORA to the
> complication
> > > of their design. This is a prime example...no filesystem on a
> platform...cmon.
> > > Not saying it's impossible, but cmon.
> > >
> > > AFAIK, no modern container prevents file I/O in an EJB. There are a few
> > > instances where file I/O can be used very effectively and easily by your
> EJBs. I
> > > say do it as long as your I/O isn't transactional. Always look for more
> > > effective and portable solutions if that is your goal. For example,
> don't read
> > > settings from an external properties file, when you can be reading them
> from
> > > JNDI.
> > >
> > > jim
> > >
> > > "Make everything as simple as possible, but no simpler" - A. Einstein
> > >
> > >
> ===========================================================================
> > > 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".
> >
> >
> ===========================================================================
> > 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".
> >
> >
>
> ===========================================================================
> 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".

===========================================================================
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".

Reply via email to