I tried very hard about 1 year ago to get FlexWiki writing
to data on a
network share.
It was very challenging, and I posted many of my findings to
the list
here. Tom, I encourage you to search the archives
diligently.
If those posts don't help, I can try and dig through my
notes and see if
there are any gems.
We ended up not using the network storage solution for a
couple reasons:
1) I couldn't get it working on IIS 5.1
2) We couldn't upgrade the server to IIS 6
Instead, we went with a solution where the wiki is stored
locally on the
server and then copied to a network share every 10 minutes
for backup.
For our installation, it proved to be good enough.
Unfortunately I don't recall the state of the attempt
before I abandoned
it.
-----Original Message-----
From: flexwiki-users-bounces lists.sourceforge.net
[mailto:flexwiki-users-bounceslists.sourceforge.net] On
Behalf Of Craig
Andera
Sent: Monday, September 25, 2006 8:35 PM
To: 'FlexWiki Users Mailing List'
Subject: Re: [Flexwiki-users] FlexWiki on network drive
Well, it's an obvious suggestion, but try flipping the pool
over to
"Network Service" without changing anything else
and see if that fixes
the Service Unavailable problem. Also, I'd check the Event
Log. ASP.NET
is pretty good about writing useful messages there when
something goes
wrong. For example, if you have a conflict between two
different ASP.NET
versions in the same app pool, it'll tell you in fairly
obvious
language. Not that I know that from having done it 20 times
or anything.
As to your broader problem, sorry, but I've just never
tried to do it
myself. I know the theory, but it's one of those
"Doctor, it hurts when
I do this."/"Then don't do that"
situations.
I'm not sure, though, why you want to host the wiki code on
a remote
file store. Since it doesn't change, it seems like it would
be better to
keep copies of it on the web server. The data is a different
story, of
course. And there you've got the whole delegation problem,
but assuming
you can solve that, it should work to have your namespaces
Rooted in a
UNC path, although I've never tried that, either.
These are all interesting cases to hear about, as I've been
reworking
*all* of the code that does all this stuff. No changes so
far that would
fix your problem, unfortunately. The caching one is a
particularly
tricky one - I think our answer on that front might simply
be "use SQL
Server", and hopefully I can implement some
improvements that use SQL
notifications or something to get the distributed part of
caching
working.
Although, now that I think of it, I can think of an easy way
to use the
new architecture to make a poor man's distributed cache -
just write a
provider that watches for updates, knows about the other
nodes in the
farm, and invalidates a topic on all nodes whenever it sees
a write.
Given how I've refactored, I could see doing something like
that in less
than 1000 lines of code. But I'm going to leave that as an
exercise for
a future developer - I need to try to stay focused (ha!) on
getting to
where I said I was going to get.
________________________________
From: flexwiki-users-bounceslists.sourceforge.net
[mailto:flexwiki-users-bounceslists.sourceforge.net] On
Behalf Of
Maddox Tom
Sent: Monday, September 25, 2006 6:58 PM
To: FlexWiki Users Mailing List
Subject: Re: [Flexwiki-users] FlexWiki on network drive
Well, that's a bummer but not an insurmountable one, since
I
just came up with a workable fallback solution for failover
if not for
load balancing. What I would really like to get going is
using remote
storage (a Windows fileserver in this case) to house the
wiki code and
content. There are a few reasons for wanting to do this,
primarily
involving disk space and redundancy. I have made some
progress and am
now getting a "Service Unavailable" error
instead of a "401: Fsck You"
error, which I think indicates a problem with the account
the
application pool is using, so I need to go look at that some
more. If
you have any thoughts on that matter, I'd love to hear
them.
TIA,
Tom
________________________________
From: flexwiki-users-bounceslists.sourceforge.net
[mailto:flexwiki-users-bounceslists.sourceforge.net] On
Behalf Of David
Ornstein
Sent: Monday, September 25, 2006 4:22 PM
To: FlexWiki Users Mailing List
Subject: Re: [Flexwiki-users] FlexWiki on network drive
It's the FlexWiki caching. And the issue isn't that it
doesn't
get written to disk immediately, it does. The issue is that
the other
instance may have a cached rendering to HTML of the Wiki
topic in
question and if it does then that cached entry will not be
invalidated
by the topic getting written to disk. Unless you have an
extremely old
build (>1year), the cache invalidation notifications are
routed
internally only to the instance doing the writing of the
topic. (And if
you have a year+ old build, you've got other problems L).
Sorry.
I'm curious about why you think you need this. Sorry, but
I
seem to have somehow lost the start of the thread...
David
From: flexwiki-users-bounceslists.sourceforge.net
[mailto:flexwiki-users-bounceslists.sourceforge.net] On
Behalf Of
Maddox Tom
Sent: Monday, September 25, 2006 4:06 PM
To: FlexWiki Users Mailing List
Subject: Re: [Flexwiki-users] FlexWiki on network drive
David,
When you say "caching," are you referring to
caching by IIS or
by FlexWiki itself? If the latter, is there a way to force
an immediate
write to disk, or am I just out of luck?
Thanks,
Tom
________________________________
From: flexwiki-users-bounceslists.sourceforge.net
[mailto:flexwiki-users-bounceslists.sourceforge.net] On
Behalf Of David
Ornstein
Sent: Monday, September 25, 2006 4:03 PM
To: FlexWiki Users Mailing List
Subject: Re: [Flexwiki-users] FlexWiki on network drive
Craig's original comment below about problems with caching
is
correct. Specifically, the way cache invalidation works
only works
within a single instance of FlexWiki. If you run two copies
of FlexWiki
on server A and server B and have their storage in a shared
location,
things won't work. Specifically, if a user changes a page
via server A,
the cache on server A will be updated correctly but not the
one on
server B.
David Ornstein
Director, Policy and Compliance Engineering
sent with Outlook 2007 beta 2 and Vista RC1
The information contained in this e-mail may be
confidential and
is intended solely for the use of the named addressee.
Access, copying or re-use of the e-mail or any information
contained therein by any other person is not authorized.
If you are not the intended recipient please notify us
immediately by returning the e-mail to the originator.(16b)
The information contained in this e-mail may be
confidential and
is intended solely for the use of the named addressee.
Access, copying or re-use of the e-mail or any information
contained therein by any other person is not authorized.
If you are not the intended recipient please notify us
immediately by returning the e-mail to the originator.(17b)
------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flexwiki-users mailing list
Flexwiki-userslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki
-users
|