<html>
<body>
<font size=3>Heh. Clearly, I should learn to edit the prefix before
posting. I blame lack of sleep :-)<br><br>
At 11:05 AM 9/25/2007, Alan Knight wrote:<br>
<blockquote type=cite class=cite cite="">Does this seem reasonable to
post?<br><br>
At 03:33 AM 9/25/2007, Philippe Marschall wrote:<br>
<blockquote type=cite class=cite cite="">> > - includes some GLORP
integration<br>
> ><br>
> Eventually, yes. That will hopefully be reasonably transparent to
the<br>
> Seaside framework.<br><br>
So there hasn't happened anything here yet in terms of integration?
Is<br>
that supposed to be VW-only or do you plan to port that to other<br>
dialects as well?</blockquote><br>
There are a number of things done at what I'd consider the experimental
level - we're still trying to figure out what the appropriate things to
do are. Actual integration as far as Seaside probably wouldn't be very
complicated. You'd need to have a mechanism by which you can get access
to a glorp session, and it might be desirable to be able to tie in
transaction boundaries with Seaside operations. More extensive is trying
to figure out what are good APIs by which people can use the facilities,
and making it easier to do things without writing out explicit metadata
any more than necessary - what I've been calling either GlorpActiveRecord
or HyperActiveRecord. I spoke at some length on some of these things at
ESUG recently. It's published in the public Store, but as I said, a lot
of it is experiments in figuring out what's appropriate to do, rather
than finished code.<br><br>
I doubt that we would port it to other dialects ourselves, but it is, and
I expect it to remain, available for other people to do so. At least
that's the way Glorp ports in general have worked to date.<br><br>
<blockquote type=cite class=cite cite="">So there won't be any kind of
special server-y, limited product that<br>
directly competes with the web edition of Gemstone/S?</blockquote><br>
As Jim Robertson posted earlier, yes, there's likely to be a
server-focused product. I don't know if you'd consider it directly
competing with Gemstone or not. Having it as a separate product, if it
happens, would be primarily for purposes of streamlining the user
experience, particularly for people who aren't already Smalltalk users.
We are looking at this as an opportunity to reach out to the broader
community. At some level it competes with Gemstone (as do any of the
server-related things we've done over the past decades) but that would be
very low on our list of priorities. I like to describe it that the
Smalltalk community is a few people in a small lifeboat on a very large
ocean, and that we are much better off rowing than trying to hit each
other with the oars.<br><br>
<br>
--<br>
Alan Knight [|], Cincom Smalltalk Development<br>
knight@acm.org<br>
aknight@cincom.com<br>
<a href="http://www.cincom.com/smalltalk" eudora="autourl">
http://www.cincom.com/smalltalk</a><br>
_______________________________________________<br>
seaside-dev mailing list<br>
seaside-dev@lists.squeakfoundation.org<br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" eudora="autourl">
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a></font>
</blockquote></body>
<br>
<div>--</div>
<div>Alan Knight [|], Cincom Smalltalk Development</div>
<div>knight@acm.org</div>
<div>aknight@cincom.com</div>
<div><a href="http://www.cincom.com/smalltalk" EUDORA=AUTOURL>
http://www.cincom.com/smalltalk</a></div>
</html>