LISTSERV mailing list manager LISTSERV 16.5

Help for XROOTD-L Archives


XROOTD-L Archives

XROOTD-L Archives


XROOTD-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

XROOTD-L Home

XROOTD-L Home

XROOTD-L  August 2004

XROOTD-L August 2004

Subject:

Re: posix-compatible client for xrootd

From:

Peter Elmer <[log in to unmask]>

Date:

23 Aug 2004 11:25:11 +0200Mon, 23 Aug 2004 11:25:11 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (122 lines)

  Hi Fabrizio,

On Mon, Aug 23, 2004 at 10:16:13AM +0200, Fabrizio Furano wrote:
>  sorry for the delay, but the department opened today. Previously I was 
> at home using the ugliest gprs. Now I am in the office booting the 
> machines...
> 
>  Is Andy coming here tomorrow?

  I thought it was Thursday. At this point we should probably just discuss
it in the weekly phone meeting tomorrow and then we can continue it if
necessary once Andy is in Padova.

                                   Pete



> Peter Elmer wrote:
> >  [Move discussion to the new xrootd mailing list from BaBar KanSOS HN]
> >
> >  Hi Fabrizio,
> >
> >  Perhaps you, Heinz and I could talk by phone briefly after lunch? Are you
> >available? Heinz, do you have any time?
> >
> >                                   Pete
> >
> >On Thu, Aug 19, 2004 at 10:35:05AM +0000, Fabrizio Furano wrote:
> >
> >>Hi all,
> >>
> >>I am back after the vacations outage....
> >>
> >>Yes, I looked at the code, and I think that the fastest way to get to 
> >>the result is to borrow some components from xrootd/heinz's client. 
> >>These could be used to substitute the few classes that TXNetfile uses 
> >>from root.
> >>
> >>I see mainly three points in the work to do, and I have answers for 
> >>two of them:
> >>
> >>- client sockets: I can build a simple socket class similar to TSocket 
> >>and use it from TXSocket.
> >>- private members coming from TNetfile/TFile: they are not many, 5-7 
> >>data members to incorporate in the new interface
> >>- Configuration flags and parameters: now they come from TEnv. What do 
> >>you suggest for them in the new client? We might use:
> >> - envvars... I know Pete says they are *evil*
> >> - pass to the ctor some optional data structure
> >> - use the default parameters as constants. After all, they have
> >>   never been changed...
> >>
> >>
> >>My suggestion, to speed up the work, is to start from the latest 
> >>TXNetFile inside root, and making it independent from the root classes 
> >>while still in the framework. When the result is reached, then we can 
> >>deal with a standalone makefile.
> >>
> >>I am not enthusiast of the idea of doing the opposite thing: starting 
> >>from another client's structure and putting inside all the other 
> >>features. I believe that this is more complicated and prone to bugs 
> >>everywhere.
> >>
> >>Fabrizio
> >>
> >>[log in to unmask] wrote:
> >>
> >>>Hi Pete,
> >>>
> >>>
> >>>
> >>>>Do you see a reason why we shouldn't just implement write() in Heinz's
> >>>>client and go from there?
> >>>
> >>>I see nothing wrong in using it as a starting point. However, we do have
> >>>some missing protocol pieces that need to be added (e.g., connection
> >>>multiplexing). I would dare say that Fabrizio should comment as well.
> >>>
> >>>
> >>>
> >>>>Ah, right. So what do we have to turn on to get the olbd's to allow
> >>>>(redirection for) writing? I see:
> >>>>
> >>>>olb.path s /store
> >>>>
> >>>>The doc on this is a bit terse. I guess that "s" actually means "rs" by
> >>>>default so I would need something like:
> >>>>
> >>>>olb.path w /whatever
> >>>>
> >>>>to allow me to write files to /kanga/whatever
> >>>
> >>>Almost right (see below). Terse, eh? You're always welcome to suggest
> >>>expansions.
> >>>
> >>>
> >>>
> >>>>? (And turn off the staging, which wouldn't be relevant in the case of
> >>>>the "output buffers", for example. In that case "whatever" would 
> >>>>actually
> >>>>be "store", but that is a detail.)
> >>>
> >>>Not quite. In fact, you really do need to say "ws" because, in fact, you
> >>>will be creating files. Temporally, it is difficult to figure wout 
> >>>whether
> >>>you are trying to update an existing file or create one from whole cloth.
> >>>So, you could get rid of "s" but then you would not be able to create any
> >>>new files. I guess I need to check what the xrootd is configured to do by
> >>>default (I know we decided this based on Objectivity years ago).
> >>>
> >>>Andy
> >



-------------------------------------------------------------------------
Peter Elmer     E-mail: [log in to unmask]      Phone: +41 (22) 767-4644
Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva 23, Switzerland
-------------------------------------------------------------------------


Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
July 2009
June 2009
May 2009
April 2009
March 2009
January 2009
December 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use