The @ is used to say "the next thing is a core name"
If we require a the core name for every request (when MultiCore is
enabled) then this would go away.
I get the feeling this is the best way to go.
ryan
Noble Paul ??? ?? wrote:
I cannot see the value add of the /@
And '@' is not
I cannot see the value add of the /@
And '@' is not a friendly URL character
--Noble
On Dec 11, 2007 8:05 PM, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> Henrib wrote:
> >
> > To be honest, I am not a big fan of the '/@corename' syntax ; I feel the
> > '?core=corename' syntax carries less surprise
I just committed a simple fix for the admin pages (rev 603269)
?core=core1 will work for /admin pages, but not for handleres.
Assuming we go with the route saying "if multi-core support is
avaliable, all requests must include the core name" It would make sense
to have:
http://localhost:8983/s
Henrib wrote:
To be honest, I am not a big fan of the '/@corename' syntax ; I feel the
'?core=corename' syntax carries less surprise and may be extended more
easily (Stu's comment in solr-350).
I've uploaded a small patch to solr-350 (solr-350.patch) so the core as a
request parameter works agai
re name out of the
> path and include it as a request attribute right?
>
>
>
>
> -Hoss
>
>
>
--
View this message in context:
http://www.nabble.com/multicore-and-admin-pages--tp14268867p14275004.html
Sent from the Solr - Dev mailing list archive at Nabble.com.
I notice this in the MultiCore wiki...
To access the admin pages for each core visit:
http://localhost:8983/solr/admin/?core=core0
http://localhost:8983/solr/admin/?core=core1
...trying this out using the example multicore setup didn't seem to work
(the admin screen said core0 even f
