=?iso-8859-2?Q?Magn=FAs_=3F=F3r_Torfason?= [EMAIL PROTECTED] writes:
I added the new properties to conf/master/TurbineResources.master. Is that
correct, or should I have added them to conf/TurbineResources.properties?
Always add properties file modifications to TurbineResources.master.
After
Magns ?r Torfason wrote:
I'd just call some setupcode and then
xmlrpcServer = new helma.xmlrpc.WebServer (555);
Which would cause a server to be started, listening on the URL
http://hostname:555/RPC2
handlers are added with
xmlrpcServer.addHandler ("handlername", new
Magnus ?or Torfason wrote:
What i'm thinking of is adding a:
registerRpcHandler(String handlerName, Object handler);
As well as adding code in the init() function to enable handlers to
be specified through the service properties.
Nice! Could you please tell how would be
I note that Turbine now includes a service for calling remote XmlRpc
functions.
I'm using a Service to provide XmlRpc _server_ functionality and would like
to contribute it to Turbine.
Would people want me to add the server functionality to the existing service
(my preference) or to provide a
on 11/23/2000 8:54 AM, "Magnus ?or Torfason" [EMAIL PROTECTED] wrote:
Would people want me to add the server functionality to the existing service
(my preference) or to provide a new service for that?
Go ahead and add that to the existing service.
-jon
--
twice of not very much is still a
I have written an xml-rpc service which I would like to be considered
for inclusion within the turbine tree.
The code can be found here -
http://static.userland.com/gems/barista/txmlrpc.jar
Also included within the jar, is a testxmlrpc.wm file (and the
corresponding .java file) which shows
I have written an xml-rpc service which I would like to be considered
for inclusion within the turbine tree.
The code can be found here -
http://static.userland.com/gems/barista/txmlrpc.jar
Also included within the jar, is a testxmlrpc.wm file (and the
corresponding .java file) which shows
On Fri, 19 May 2000, you wrote:
Would a user request a certain url whether from a browser or a WebDAV client
for example?
The browser must support WebDAV.
The class that coresponds with the url would handle the POST'd
data and would 'work' accordingly.
Yes, something along those lines.
On Fri, 19 May 2000, you wrote:
Have you looked at exploring integration possibilities with the new Jakarta
sub-project Slide http://jakarta.apache.org/slide/index.html?
No, I was totally unaware of this - the project must of just started.
Anyway, the Turbine-WebDAV stuff is just an idea,
