<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Ben Clifford wrote:
<blockquote
cite="mid:Pine.LNX.4.64.0705231637230.22628@dildano.hawaga.org.uk"
type="cite">
<pre wrap="">
On Wed, 23 May 2007, Ioan Raicu wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hmmm... from my understanding, the Falkon provider is independent of the fact
that Swift will actually use Falkon or not. There is no requirement that
Falkon be used, even if you have the Falkon provider installed!
</pre>
</blockquote>
<pre wrap=""><!---->
Hopefully its that way, configurable by eg. a site catalog setting. I
don't know if that is the case though right now. If not, we should make it
that way.
</pre>
<blockquote type="cite">
<pre wrap="">About how Falkon gets deplyed, it is simply uncompressed, you modify 1 or 2
config files, and use the included scripts to start everything! All this is
in the included readme.txt in the Falkon archive, downloadable online on my
web site. Once again, if someone is not intersted in using Falkon, then I see
no reason why they would be doing anything different than before just because
there is now a Falkon provider in Swift.
</pre>
</blockquote>
<pre wrap=""><!---->
ok. Does the swift/falkon provider need to be told an EPR to the Falkon
web service?
</pre>
</blockquote>
No, it creates a new resource for which the EPR is returned, and that
is used over and over again until Swift shuts down and the resource is
destroyed. Basically, the service URL is all is needed!<br>
<blockquote
cite="mid:Pine.LNX.4.64.0705231637230.22628@dildano.hawaga.org.uk"
type="cite">
<pre wrap="">
My concerns mostly are not so much about having a provider in the source
tree when people aren't going to use; that's fine. But the code needs to
not be in the form of some random jar file without it being clear where it
came from. If the code can build without needing Falkon code around (which
I suspect it can't), then its simple to put it in the Swift codebase. If
it has Falkon build dependencies (eg for web service stubs) then thats
more stuff accumulating in the codebase that needs long term management
(and brings in incompatibilities if you want to modify the Falkon web
services API)
</pre>
</blockquote>
I was able to generate stubs from a command line tool bundled with GT4
a while back, so I don't see why you couldn't just have it all Falkon
independent!<br>
<br>
Ioan<br>
<br>
<pre class="moz-signature" cols="72">--
============================================
Ioan Raicu
Ph.D. Student
============================================
Distributed Systems Laboratory
Computer Science Department
University of Chicago
1100 E. 58th Street, Ryerson Hall
Chicago, IL 60637
============================================
Email: <a class="moz-txt-link-abbreviated" href="mailto:iraicu@cs.uchicago.edu">iraicu@cs.uchicago.edu</a>
Web: <a class="moz-txt-link-freetext" href="http://www.cs.uchicago.edu/~iraicu">http://www.cs.uchicago.edu/~iraicu</a>
<a class="moz-txt-link-freetext" href="http://dsl.cs.uchicago.edu/">http://dsl.cs.uchicago.edu/</a>
============================================
============================================
</pre>
</body>
</html>