I'm pretty sure I saw this a long time ago, but BugRat is either down or
reeeally slow, so I can't search for it.
I originally set the HTTP port to 8080, but then to 20001 so any
port-scanning jokers on Rogers/Shaw cable wouldn't hit on the defaults.
After I restarted the server, it still uses/cr
Does anyone have any opinions on a process for making commits to the 3.2 branch? Now
that I've got my new fancy committer status, I'd like to check in some bug fixes there
(to mod_jk / ajp13). However, before I do that, I wanted to check if there is anyone
who is functioning as a Release Mana
danmil 00/12/25 14:31:58
Modified:src/native/mod_jserv autochange.c
Log:
Converted C++-style comments to C-style comments to fix build on Sparc.
Revision ChangesPath
1.2 +23 -21jakarta-tomcat/src/native/mod_jserv/autochange.c
Index: autochange.c
===
danmil 00/12/25 14:30:46
Modified:src/native/apache/jserv Tag: tomcat_32 autochange.c
Log:
Converted C++-style comments to C-style comments to fix build on Sparc.
Revision ChangesPath
No revision
No revision
1.1.6.1
Brett Bergquist typed the following on 08:51 AM 12/25/2000 -0500
>Keif, have you considered using JavaSpace's as a shared storage mechanism.
>I've just read some things on this and it seems like it might be a fit, but
>I've not played with this yet. Just a thought. BTW, there is a good
>article
I think someone already has been assigned to implement
a session store for javaspaces. Check out the action
items for Catalina.
Dave
--- Brett Bergquist <[EMAIL PROTECTED]> wrote:
> Keif, have you considered using JavaSpace's as a
> shared storage mechanism.
> I've just read some things on this a
Keif, have you considered using JavaSpace's as a shared storage mechanism.
I've just read some things on this and it seems like it might be a fit, but
I've not played with this yet. Just a thought. BTW, there is a good
article on this in one of the fairly recent Java Developer's Journal.
-O
I have a bit of fear that you're getting into extremely complex waters here, and I
want to be sure you focus on the most useful bits first. Any form of distributed
synchronization of data is very difficult to get right, IMHO. Which is not to say
that it shouldn't be done, nor that your ideas
Hi Shai,
Thanks for your patch, it's a very good start and I think it'll be useful
for many users.
I think it needs some more work - I'm not talking about the main
functionality you are implementing, which I'm sure will be tested and
improved and will have a nice evolution.
I'm talking as a p
