James and Julian,<br><br>Thanks very much for the responses. I'll have a look at 2.9 and see if there are are any opportunities for reuse. I am interested in using Magritte for my domain model and I'll be checking out some of the patterns for session management etc. <br>
<br>I'm tempted to use GemStone because it's familiar to me, but I think my persistence requirements are fairly basic (famous last words). I'll be starting with the simplest thing that will work, and HTTP is well-supported. I'll be avoiding the Dark Forest of XML but other that I'm keeping an open mind. <br>
<br>I'll let you know if Seaside presents any interesting synergies. It seems there should be some benefits as this is fundamentally no different than a web app with different transport and presentation components (and, er, synchronized state among all clients).<br>
<br>I'm thinking I need signed and validated requests, but I'll dig more into that before I raise any specific questions.<br><br>Steve<br><br><div class="gmail_quote">On Thu, Mar 5, 2009 at 10:36 PM, Julian Fitzell <span dir="ltr"><<a href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Steve,<br>
<br>
As long as it "makes sense" to use HTTP for what you're doing, Seaside<br>
may be a good fit. If you're not doing HTML, some pieces will be of<br>
less use to you but you can generate documents in any format you like<br>
and even leverage the Session logic if desired. You're walking off the<br>
well-trodden path, though, so you'll have to be prepared to dig in a<br>
bit and ask questions if you can't figure out where to plug in.<br>
Hopefully 2.9, with its clarified architecture, will help make this<br>
clearer.<br>
<br>
I can't say from what you posted whether Seaside is right for your use<br>
case or not but you can always just start writing something in<br>
Smalltalk and see if and when you want HTTP. Or as James says, you can<br>
start writing it in HTTP and see whether you need something else. :)<br>
<font color="#888888"><br>
Julian<br>
</font><div><div></div><div class="h5"><br>
On Fri, Mar 6, 2009 at 3:14 AM, Steve Wart <<a href="mailto:steve.wart@gmail.com">steve.wart@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
> I just listened to James Robertson's interview with Julian Fitzell today and<br>
> I thought it was great.<br>
><br>
> I'd like to set up an server for an iPhone app that might have an HTTP<br>
> component for some features but for the most part it won't be web-based<br>
> (I'll probably be using Objective-C and some WebKit views with Javascript).<br>
><br>
> It seems that Seaside is the right choice but I'm wondering if anyone has<br>
> any suggestions about how I might approach the problem.<br>
><br>
> In general, I am thinking about a game server type of environment that<br>
> supports the following sorts of interactions:<br>
><br>
> * secure user authentication<br>
> * create or join an existing game (basic app logic)<br>
> * navigate around with a WebView using a Google JavaScript API<br>
> (probably with custom controls overlayed either as divs or native iPhone<br>
> components calling Javascript from Obj-C)<br>
> * maintain a shared domain model for the connected users within a game,<br>
> distinct from other sessions that may be running<br>
> * keep track of various attributes associated with the user sessions (e.g.<br>
> current IP address, GIS coordinates)<br>
><br>
> Is this an appropriate use of Seaside or would I be better of just starting<br>
> from scratch with GemStone or Magma?<br>
><br>
> I definitely want the "brains" of my app in Smalltalk<br>
><br>
> Cheers,<br>
> Steve<br>
><br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> seaside mailing list<br>
> <a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
> <a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
><br>
><br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div><br>